|
From: Gupta R. <Ri...@fr...> - 2008-04-03 11:29:58
|
==115== Memcheck, a memory error detector.
==115== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==115== Using LibVEX rev 1804, a library for dynamic binary translation.
==115== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==115== Using valgrind-3.3.0, a dynamic binary instrumentation framework.
==115== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==115== For more details, rerun with: -v
==115==
dis_proc_ctl(ppc)(mfspr,SPR)(0x11F)
disInstr(ppc): unhandled instruction: 0x7C1F42A6
primary 31(0x1F), secondary 678(0x2A6)
==115== valgrind: Unrecognised instruction at address 0x40144F8.
==115== Your program just tried to execute an instruction that Valgrind
==115== did not recognise. There are two possible reasons for this.
==115== 1. Your program has a bug and erroneously jumped to a non-code
==115== location. If you are running Memcheck and you just saw a
==115== warning about a bad jump, it's probably your program's fault.
==115== 2. The instruction is legitimate but Valgrind doesn't handle it,
==115== i.e. it's Valgrind's fault. If you think this is the case or
==115== you are not sure, please let us know and we'll try to fix it.
==115== Either way, Valgrind will now raise a SIGILL signal which will
==115== probably kill your program.
==115==
==115== Process terminating with default action of signal 4 (SIGILL)
==115== Illegal opcode at address 0x40144F8
==115== at 0x40144F8: _dl_sysdep_start (in /lib/ld-2.5.so)
==115== by 0x4002344: _dl_start_final (in /lib/ld-2.5.so)
==115== by 0x4002898: _dl_start (in /lib/ld-2.5.so)
==115== by 0x4015114: _start (in /lib/ld-2.5.so)
==115==
==115== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 1)
==115== malloc/free: in use at exit: 0 bytes in 0 blocks.
==115== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==115== For counts of detected errors, rerun with: -v
==115== All heap blocks were freed -- no leaks are possible.
Illegal instruction |
|
From: Julian S. <js...@ac...> - 2008-05-08 13:48:40
|
Richa, I'm just collecting up bugs to fix (!) I can look at this one if useful. If so it will help if you can send me the /lib/ld-2.5.so from the machine on which you got this error. J On Thursday 03 April 2008 13:29, Gupta Richa wrote: > Hi > I am cross-compiling the valgrind for ppc-32 and I am getting the > following error while using valgrind with my executables. > is_proc_ctl(ppc)(mfspr,SPR)(0x11F) > disInstr(ppc): unhandled instruction: 0x7C1F42A6 > primary 31(0x1F), secondary 678(0x2A6) > ==115== valgrind: Unrecognised instruction at address 0x40144F8. > ==115== Your program just tried to execute an instruction that Valgrind > ==115== did not recognise. There are two possible reasons for this. > ==115== 1. Your program has a bug and erroneously jumped to a non-code > ==115== location. If you are running Memcheck and you just saw a > ==115== warning about a bad jump, it's probably your program's fault. > ==115== 2. The instruction is legitimate but Valgrind doesn't handle it, > ==115== i.e. it's Valgrind's fault. If you think this is the case or > ==115== you are not sure, please let us know and we'll try to fix it. > ==115== Either way, Valgrind will now raise a SIGILL signal which will > ==115== probably kill your program. > ==115== > ==115== Process terminating with default action of signal 4 (SIGILL) > ==115== Illegal opcode at address 0x40144F8 > ==115== at 0x40144F8: _dl_sysdep_start (in /lib/ld-2.5.so) > ==115== by 0x4002344: _dl_start_final (in /lib/ld-2.5.so) > ==115== by 0x4002898: _dl_start (in /lib/ld-2.5.so) > ==115== by 0x4015114: _start (in /lib/ld-2.5.so) > > Attached is the log for the same. Please do tell me what is the mistake. > > Thanks & Regards, > Richa |