On Wed, 2012-06-20 at 16:09 -0400, Bob Rossi wrote:
Hi,
I'm using valgrind with a C++ program that embeds python.
The stack trace is pretty deep, greater than 50 at almost every
point valgrind finds a memory leak.
Unfortunately, I can't see the stack frame that started this
chain
vex and64-IR: unhandled instruction bytes: 0xDA 0xE9 0xDF 0xE0
I checked and this turns out to be a fragment in the __ieee754_powl() routine
executing these two instructions:
fucompp
fnstsw
I checked Bugzilla, it doesn't seem listed in the bugs database already.
Thank you
vex and64-IR: unhandled instruction bytes: 0xDA 0xE9 0xDF 0xE0
valgrind: Unrecognized instruction at address: 0x3411235BF4.
Illegal opcode at address 0x3411235BF4:
at 0x3411235BF4: __ieee754_powl (in /lib64/libm-2.5.so)
I checked and this turns out to be a fragment in the
