This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc 3.1 and gdb 5.2?


Hello,

We are stuck after a variety of experiments.
We tried gdb 5.1.1 and gdb 5.2, and we used
the latest gnu ld from binutils-2.12.

When using gdb 5.2, setting a breakpoint in
gdb results in immediate core dump.

When using gdb 5.1.1, setting a breakpoint
takes effect, but when we try to run, we
get a message about libstdc++.so.4: open failed.
This in spite of every possible manipulation
of $LD_LIBRARY_PATH.  Some transcript
exists below to show what's happening.

Looks like we'll have to give up on using gcc 3.1
on Solaris until someone makes a breakthrough
with gdb.

Thanks for your help and advice.

Regards,
Doug

doug@heaven<41> gdb bin/shifter.mctsim
GNU gdb 5.1.1
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 "sparc-sun-solaris2.8"...
(gdb) b main
Breakpoint 1 at 0x45218: file System.cxx, line 126.
(gdb) run
Starting program: /home/doug/unixtest/shifter/bin/shifter.mctsim 
ld.so.1: /home/doug/unixtest/shifter/bin/shifter.mctsim: fatal: libstdc++.so.4: open failed: No such file or directory

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) quit
doug@heaven<42> ls -l $LD_LIBRARY_PATH
total 15960
-rw-r--r--    1 scm      scm           519 Jun 10 14:26 charset.alias
drwxrwxr-x    3 scm      scm          4096 Jun 10 14:23 gcc-lib/
lrwxrwxrwx    1 scm      scm            13 Jun 10 14:24 libgcc_s.so -> libgcc_s.so.1
-rw-r--r--    1 scm      scm        802264 Jun 10 14:24 libgcc_s.so.1
-rw-r--r--    1 scm      scm        220968 Jun 10 14:40 libiberty.a
-rw-r--r--    1 scm      scm       7408752 Jun 10 14:33 libstdc++.a
-rwxr-xr-x    1 scm      scm          1112 Jun 10 14:33 libstdc++.la*
lrwxrwxrwx    1 scm      scm            18 Jun 13 12:43 libstdc++.so -> libstdc++.so.4.0.0*
lrwxrwxrwx    1 scm      scm            18 Jun 13 12:43 libstdc++.so.4 -> libstdc++.so.4.0.0*
-rwxr-xr-x    1 scm      scm       7183740 Jun 10 14:33 libstdc++.so.4.0.0*
-rw-r--r--    1 scm      scm        673056 Jun 10 14:33 libsupc++.a
-rwxr-xr-x    1 scm      scm          1024 Jun 10 14:33 libsupc++.la*
drwxrwxr-x    2 scm      scm          4096 Jun 10 14:40 sparcv9/


Doug Warmke wrote:
> 
> Guys,
> 
> I noticed on the main gcc-3.1 page that the Solaris platform
> is not yet making use of dwarf object format.  It's interesting that
> you are experiencing the same problem on cygwin as I am experiencing
> on Solaris 7 and 8.
> 
> We are currently experimenting with the latest available GNU ld
> and gdb 5.1.1.  Will keep you posted tomorrow.
> 
> Regards,
> Doug
> 
> > From <dylan@q-games.com>(________-000000086447) Thu Jun 13 00:54:10 2002
> >
> > Hello there,
> >
> > My next stop was going to be the gdb and cygwin lists, however, gcc is the
> > more complicated and experimental of the other two and I wanted to see if
> > anyone else was experiencing problems on other platforms too.
> >
> > I compiled and installed the latest binutils which contains ld of course,
> > do you think it might be a problem with ld on cygwin?   If so, I'd better
> > add "ld" to my list of mailing lists to post to :-(
> >
> > I haven't re-compiled cygwin itself into the dwarf2 format (don't know if
> > its possible), do you think there might be problems with the linker linking
> > together 2.95-3 compiled older libraries with 3.1 compiled dwarf2 ones?
> >
> > Regards
> >
> > ---------------------------------
> > Q-Games, Dylan Cuthbert.
> > http://www.q-games.com
> >
> > ----- Original Message -----
> > From: "Rob Taylor" <robt@flyingpig.com>
> > To: "Dylan Cuthbert" <dylan@q-games.com>; "Doug Warmke" <doug@ikos.com>;
> > <gcc@gnu.org>
> > Sent: Wednesday, June 12, 2002 10:57 PM
> > Subject: RE: gcc 3.1 and gdb 5.2?
> >
> >
> > > have you tried asking on the cygwin and gdb mailing lists to see if anyone
> > > theres experienced similar problems?  sounds like there might be some
> > problem
> > > with gdb interacting with cygwin's ld implementation when using dwarf2...
> > >
> > > > -----Original Message-----
> > > > From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
> > > > Dylan Cuthbert
> > > > Sent: Wednesday, June 12, 2002 11:26 AM
> > > > To: Rob Taylor; Doug Warmke; gcc@gnu.org
> > > > Subject: Re: gcc 3.1 and gdb 5.2?
> > > >
> > > >
> > > > I have tried re-winding to 5.1.1 but still have problems single stepping
> > > > even a standard C++ Hello World program.  It does get to the first line
> > of
> > > > code, but single stepping over library calls causes gdb to freeze.
> > > >
> > > > System is Cygwin 1.3.10, gcc 3.1 (pre-release or release), gdb 5.1.1/5.2
> > > >
> > > > Regards
> > > >
> > > > ---------------------------------
> > > > Q-Games, Dylan Cuthbert.
> > > > http://www.q-games.com
> > > >
> > > > ----- Original Message -----
> > > > From: "Rob Taylor" <robt@flyingpig.com>
> > > > To: "Doug Warmke" <doug@ikos.com>; <gcc@gnu.org>
> > > > Sent: Wednesday, June 12, 2002 6:35 PM
> > > > Subject: RE: gcc 3.1 and gdb 5.2?
> > > >
> > > >
> > > > > I've actually observed similar crashes with gdb5.2 and gcc 3.0.4!
> > > > (specifically
> > > > > the 20020401 cvs snaphot of gdb used by debian). Rewinding to 5.1.1
> > solved
> > > > issue
> > > > > for me.
> > > > >
> > > > > Rob Taylor
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf
> > Of
> > > > > > Doug Warmke
> > > > > > Sent: Wednesday, June 12, 2002 6:06 AM
> > > > > > To: gcc@gnu.org
> > > > > > Subject: gcc 3.1 and gdb 5.2?
> > > > > >
> > > > > >
> > > > > >
> > > > > > GCC Team,
> > > > > >
> > > > > > We recently installed gcc 3.1 and have successfully built our tree.
> > > > > > When we try to debug using gdb 5.2, we get a core dump whenever
> > > > > > trying to set a breakpoint.   This is occuring on both Solaris 7
> > > > > > and Solaris 8.  Our code is C++ (not C).  A sample transcript
> > > > > > is shown below.
> > > > > >
> > > > > > Are there any known issues using this combination of GNU tools?
> > > > > > Do we have to enable any special configuration or compiler options?
> > > > > > The only thing I found on gcc.gnu.org was that gdb 5.1.1 or higher
> > > > > > is required for debugging gcc 3.1 compiled code.
> > > > > >
> > > > > > Thanks and regards,
> > > > > > Doug Warmke
> > > > > > (408) 284-8554
> > > > > >
> > > > > > > > > Sorry, but it is still seg-faulting when I try to set a
> > > > breakpoint.
> > > > > > > > >
> > > > > > > > > jlo% /hq/scmtools/Test/SunOS5.8/bin/gdb shifter.mctsim
> > > > > > > > > GNU gdb 5.2
> > > > > > > > > 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 "sparc-sun-solaris2.8"...
> > > > > > > > > (gdb) b main
> > > > > > > > > Segmentation Fault
> > > > > > > > > jlo%
> > > > > >
> > > > >
> > > >
> > >
> >
> >


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]