|
From: <ar...@de...> - 2004-03-27 03:45:33
|
Package: valgrind
Version: 1:2.1.1-2
Severity: normal
Valgrind dies reading debug symbols from C++ exectuables compiled with
-gstabs+. To reproduce, compile the following C++ code with the
-gstabs+ flag and run valgrind on the resulting executable:
#include <iostream>
#include <vector>
int main()
{
std::vector<int> v;
v.push_back(1);
v.push_back(2);
for (std::vector<int>::iterator iter = v.begin(); iter != v.end();
++iter)
std::cout << *iter << std::endl;
return 0;
}
I get the following output from valgrind for the above example:
==26875== Memcheck, a memory error detector for x86-linux.
==26875== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==26875== Using valgrind-2.1.1, a program supervision framework for
x86-linux.
==26875== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
@@ don't know what type ':' is
@@ parsing
:_Lock:Tt(128,76)=s1operator=::(128,77)=#(128,76),(128,78)=&(128,76),(128,79)=*(128,76),(128,80)=&(128,81)=k(128,76),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockaSERKS1_;2A.;__base_ctor::(128,82)=#(128,76),(0,19),(128,79),(128,80),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC2ERKS1_;2A.;__comp_ctor::(128,82):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC1ERKS1_;2A.;__base_ctor::(128,83)=#(128,76),(0,19),(128,79),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC2Ev;2A.;__comp_ctor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC1Ev;2A.;__base_dtor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockD2Ev;2A.;__comp_dtor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockD1Ev;2A.;;
gave NULL type
(_Lock:Tt(128,76)=s1operator=::(128,77)=#(128,76),(128,78)=&(128,76),(128,79)=*(128,76),(128,80)=&(128,81)=k(128,76),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockaSERKS1_;2A.;__base_ctor::(128,82)=#(128,76),(0,19),(128,79),(128,80),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC2ERKS1_;2A.;__comp_ctor::(128,82):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC1ERKS1_;2A.;__base_ctor::(128,83)=#(128,76),(0,19),(128,79),(0,19);:_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC2Ev;2A.;__comp_ctor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockC1Ev;2A.;__base_dtor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockD2Ev;2A.;__comp_dtor::(128,83):_ZNSt24__default_alloc_templateILb1ELi0EE5_LockD1Ev;2A.;;
remains)
--26875-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--26875-- si_code=1 Fault EIP: 0xB803E79F (); Faulting address: 0x0
valgrind: the `impossible' happened:
Killed by fatal signal
Basic block ctr is approximately 0
==26875== at ???
==26875== by ???
==26875== by ???
==26875== by ???
sched status:
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==26875== at ???
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.
Also, I'm using version 3.3.3-1 of the Debian g++-3.3 package.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-1-686-smp
Locale: LANG=C, LC_CTYPE=C
Versions of packages valgrind depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
-- no debconf information
|
|
From: <ar...@de...> - 2004-03-27 03:45:36
|
I've already filed a bug but I submit the problem here too. |