----- Original Message ----- > > > Hi, > I got the crash up on the target but I get following error. Well, that's impressive... > WARNING: kernels compiled by different gcc versions: > ./vmlinux: (unknown) > live system kernel: 4.4.3 That's a harmless warning, but what do these commands show: $ strings vmlinux | grep "Linux version" and $ cat /proc/version The gcc-related data in those two strings are being compared. > crash: cannot open secondary temporary file When do you see that message? > > I have taken System.map and vmlinux from the same build path. The System.map file is not necessary if the vmlinux is the kernel that the live system is running. Dave > > Regards, > Oza. > > > > > > From: Dave Anderson <anderson@xxxxxxxxxx> > To: paawan oza <paawan1982@xxxxxxxxx>; "Discussion list for crash > utility usage, maintenance and development" > <crash-utility@xxxxxxxxxx> > Sent: Monday, 6 August 2012 8:58 PM > Subject: Re: using crash for ARM > > > > ----- Original Message ----- > > > > > > > > Hi, > > > > > > I would like to use crash utility on ARM. > > what I understand is there might be two ways to go about it. > > > > 1) cross compile whole crash for arm itself, which doesnt seem to > > be > > good option because on arm target we will need lots of depedent > > packages. > > > > 2) run crash on x86 and have gdbserver/remoter server compiled on > > target. and have serial connection and so on.. > > > > please suggest instructions or any pointers regarding the same. > > > > Regards, > > Oza. > > If you are talking about running crash on a live ARM system, then > option #1 is the only possibility. Option #2 does not exist for > the crash utility; live system access requires either /dev/mem, > /proc/kcore, or the /dev/crash misc driver. > > Dave > > > > -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility