Bug#176797: libstdc++5: GDB looks in the wrong place for libstdc++ headers
On Fri, Jan 17, 2003 at 09:32:38AM -0500, Daniel Jacobowitz wrote:
> On Wed, Jan 15, 2003 at 05:13:14PM -0600, Daniel E Baumann wrote:
> > On Wed, Jan 15, 2003 at 03:05:55PM -0500, Daniel Jacobowitz wrote:
> > > On Wed, Jan 15, 2003 at 02:15:04AM -0600, Daniel E Baumann wrote:
> > > > Package: libstdc++5
> > > > Version: 1:3.2.2-0pre5
> > > > Severity: important
> > > >
> > > > When running my c++ program from inside gdb I get the following:
> > > >
> > > > danielb@frodo:~/software/src/cvs/gsim/src/examples/mm1$ gdb .libs/mm1
> > > > GNU gdb 5.3-debian
> > > > Copyright 2002 Free Software Foundation, Inc.
> > > > GDB is free software, covered by the GNU General Public License, and you
> > > > are
> > > > welcome to change it and/or distribute copies of it under certain
> > > > conditions.
> > > > Type "show copying" to see the conditions.
> > > > There is absolutely no warranty for GDB. Type "show warranty" for
> > > > details.
> > > > This GDB was configured as "i386-linux"...
> > > > (gdb) run
> > > > Starting program:
> > > > /home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
> > > > [New Thread 16384 (LWP 20311)]
> > > >
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > [Switching to Thread 16384 (LWP 20311)]
> > > > 0x400313b6 in bool std::has_facet<std::ctype<char> >(std::locale
> > > > const&) (__loc=@0x804dc48)
> > > > at /usr/include/g++-v3/bits/locale_facets.tcc:87
> > > > 87 /usr/include/g++-v3/bits/locale_facets.tcc: No such file or
> > > > directory.
> > > > in /usr/include/g++-v3/bits/locale_facets.tcc
> > >
> > > That's not enough information. How was this built? What libraries is
> > > it really linked to? What headers are really opened during build?
> > It was built with g++-3.2 so it is linked to libstdc++5 (well, and my
> > lib gsim, gnu common c++ built from cvs and gnu scientific
> > library, etc.). It uses the headers in /usr/include/c++/3.2 which is where
> > they are for libstdc++5[-dev], AFAIK.
> OK, so that's not it. What file actually includes the path g++-v3?
> Just check using GNU grep. It might be one of your libraries.
No files include g++-v3. I grepped and got nothing. This makes sense
becase those headers are from libstc++3, IIRC, which I am not using. I
don't understand why gdb wants to pull headers from there. This makes
no sense to me.