|
From: Sree O. <so...@vm...> - 2005-08-19 00:03:45
|
# Platform on which valgrind is built $ uname -a Linux soggu-bld.vmware.com 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST = 2003 i686 i686 i386 GNU/Linux # compiler version $ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=3D/usr --mandir=3D/usr/share/man --infodir=3D/usr/share/info --enable-shared --enable-threads=3Dposix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=3Di386-redhat-linux Thread model: posix gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) When I used this valgrind on a simple file (valgrind ls). it worked = fine. But when I tried to use it on our product (a MT server that loads shared libraries using dlopen) it crashes with the following message. vex x86->IR: unhandled instruction bytes: 0xF0 0xF 0xC7 0xE Process terminating with default action of signal 4 (SIGILL): dumping = core Is there a known work around for this ? Sree |