From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, mn216@columbia.edu
Cc: gdb@sources.redhat.com
Subject: Re: help: gdb and c++ strings
Date: Thu, 05 Dec 2002 20:45:00 -0000 [thread overview]
Message-ID: <200212060445.gB64j7d21501@duracef.shout.net> (raw)
Hello Murad,
There are two snapshots available:
ftp://sources.redhat.com/pub/gdb/snapshots/branch/gdb-5.2.91.tar.bz2
ftp://sources.redhat.com/pub/gdb/snapshots/current/insight+dejagnu-weekly-CVS-20021206.tar.bz2
The first snapshot is from the 5.3 branch and will become gdb 5.3 soon
if everything goes well. I am regression testing this right now versus
5.2.1 and there are no big obvious problems yet.
The second snapshot is from the CVS head. It's more likely to have the
bug fix that Daniel J is referring to. It's also possible that it has
build problems because the configuration+build machinery is in active
development right now. If it builds, though, it is also in good shape
for gcc v3 dwarf-2 debugging.
You are on the right track with gcc 3.2.1 and -gdwarf-2.
I recommend you try the "branch" snapshot first; it is much more stable.
If it is not featureful enough (does not fix your problems) then try
the "current" snapshot.
Hope this helps,
Michael C
P. S. I see you are at columbia.edu. I am on Staten Island. Isn't
the city beautiful with today's snow?
next reply other threads:[~2002-12-06 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:45 Michael Elizabeth Chastain [this message]
2002-12-05 22:25 ` Murad Nayal
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 20:07 Murad Nayal
2002-12-05 20:15 ` Daniel Jacobowitz
2002-12-05 20:23 ` Murad Nayal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212060445.gB64j7d21501@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mn216@columbia.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox