Version:           2.1.1 (using KDE KDE 3.2.2)
Installed from:    00
Compiler:          gcc version 2.96 
OS:                Linux

Valgrind can not trace my program which runs normal,
The output message is following:

==11249== Memcheck, a memory error detector for x86-linux.
==11249== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==11249== Using valgrind-2.1.1, a program supervision framework for x86-linux.
==11249== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
 @@ don't know what type '_' is
 @@ parsing __lt__C14_Bit_referenceRC14_Bit_reference;2B.;flip::(178,12)=##(0,21);:;2A.;; gave NULL type (_lt__C14_Bit_referenceRC14_Bit_re
ference;2B.;flip::(178,12)=##(0,21);:;2A.;; remains)

 @@ expected ':' at struct method MANGLE-ARGS (remains="lt__C14_Bit_referenceRC14_Bit_reference;2B.;flip::(178,12)=##(0,21);:;2A.;;")
 @@ parsing (178,1)=s8_M_p:(178,2)=*(0,4),0,32;_M_mask:(0,4),32,32;_Bit_reference::(178,3)=##(178,4)=*(178,1);:RC14_Bit_reference;2A.(178,5
)=##(178,4);:PUiUi;2A.(178,6)=##(178,4);:;2A.;__opb::(178,7)=##(0,12);:;2B.;operator=::(178,8)=##(178,9)=&(178,1);:__as__14_Bit_referenceb;
2A.(178,10)=##(178,9);:__as__14_Bit_referenceRC14_Bit_reference;2A.;operator==::(178,11)=##(0,12);:__eq__C14_Bit_referenceRC14_Bit_referenc
e;2B.;operator<::(178,11):__lt__C14_Bit_referenceRC14_Bit_reference;2B.;flip::(178,12)=##(0,21);:;2A.;; gave NULL type (s8_M_p:(178,2)=*(0,
4),0,32;_M_mask:(0,4),32,32;_Bit_reference::(178,3)=##(178,4)=*(178,1);:RC14_Bit_reference;2A.(178,5)=##(178,4);:PUiUi;2A.(178,6)=##(178,4)
;:;2A.;__opb::(178,7)=##(0,12);:;2B.;operator=::(178,8)=##(178,9)=&(178,1);:__as__14_Bit_referenceb;2A.(178,10)=##(178,9);:__as__14_Bit_ref
erenceRC14_Bit_reference;2A.;operator==::(178,11)=##(0,12);:__eq__C14_Bit_referenceRC14_Bit_reference;2B.;operator<::(178,11):__lt__C14_Bit
_referenceRC14_Bit_reference;2B.;flip::(178,12)=##(0,21);:;2A.;; remains)
--11249-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--11249-- si_code=1 Fault EIP: 0xB8038BBB (); Faulting address: 0x0

valgrind: the `impossible' happened:
   Killed by fatal signal
Basic block ctr is approximately 0
==11249==    at 0xB802BA97: ???
==11249==    by 0xB802BA96: ???
==11249==    by 0xB802BAAC: ???
==11249==    by 0xB803185A: ???

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==11249==    at 0x3C000B40: ???


Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.

If that doesn't help, please report this bug to: valgrind.kde.org

In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using.  Thanks.


Linux version 2.4.18-18.7.x (bhcompile@bugs.devel.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)) #1 Wed Nov 13 19:30:
43 EST 2002