|
From: CHEN H. l. <Hon...@al...> - 2011-06-30 09:19:44
|
Thanks a lot. Unfortunately the board I run valgrind on is not installed with gdb because of limited memory and stroage space. We are trying NFS though...
-----Original Message-----
From: John Reiser [mailto:jr...@bi...]
Sent: 2011年6月29日 10:37
To: val...@li...
Subject: Re: [Valgrind-users] Segmentation fault on ppc
> I managed to cross-compile valgrind for linux on ppc (MPC8313), but
> failed to run it. Below is the err info caught by strace.
> What's wrong with it? Thanks in advance.
> BTW, the configure options are like:
> configure --host=powerpc-unknown-linux --target=powerpc-unknown-linux
> --prefix=/tmp/valgrind-install --build=i486-cross-linux-gnu
> --- {si_signo=SIGILL, si_code=ILL_ILLOPC, si_addr=0x38033634} (Illegal
> instruction) ---
> --- {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} (Segmentation
> fault) ---
> +++ killed by SIGSEGV +++
strace says that the instruction at address 0x38033634 is not legal on this particular CPU model, which you say is MPC8313.
What does /proc/cpuinfo say?
Because the culprit is known to be an illegal instruction, then run under a debugger such as gdb, and find out exactly what instruction that is.
$ gdb valgrind
(gdb) run
<<SIGSEGV>>
(gdb) bt
(gdb) x/x $pc
(gdb) x/i $pc
(gdb) x/8i $pc-4*4
(gdb) info reg
(gdb) x/16x $sp
--
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|