[Valgrind-users] Valgrind crashes

[Duzlevski, O. <duz...@mi...>]

Hi all,

I am trying to debug a multithreaded C app I wrote. When running through =
valgrind, it crashes with the following:

=3D=3D31036=3D=3D
--31036-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - =
exiting
--31036-- si_code=3D2 Fault EIP: 0xB002D3C2; Faulting address: =
0xB126EFF8

valgrind: the `impossible' happened:
   Killed by fatal signal
Basic block ctr is approximately 254200000
=3D=3D31036=3D=3D    at 0xB002FFDF: vgPlain_core_panic =
(vg_mylibc.c:1156)
=3D=3D31036=3D=3D    by 0xB002FFDE: panic (vg_mylibc.c:1152)
=3D=3D31036=3D=3D    by 0xB002FFFF: vgPlain_core_panic =
(vg_mylibc.c:1157)
=3D=3D31036=3D=3D    by 0xB00374B0: vg_sync_signalhandler =
(vg_signals.c:2191)

I am using Valgrind 2.2.0, --tool=3Dmemcheck --leak-check=3Dyes =
--show-reachable=3Dyes --error-limit=3Dno

Is this an internal valgrind problem? When I run my application without =
valgrind it does not crash and produces expected results.

Ognen