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 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]