From: Mike Simons <msimons@saic1.com>
To: dan@cssgroup.com (D. Bernstein)
Cc: egcs@cygnus.com
Subject: Re: debugging for egcs
Date: Fri, 20 Feb 1998 16:12:00 -0000 [thread overview]
Message-ID: <199802202236.RAA00322@aura.saic1.com> (raw)
In-Reply-To: <34EDB473.7C97@cssgroup.com>
Daniel J. Bernstein wrote:
> Where can I get a reliable debugger that works with egcs 1.0.1?
> I am currently using GNU gdb 4.16, and frankly, it is pitiful when
> used with EGCS.
Dan,
I can't say these are much better, but _some_ things work better.
In my experience trying to debug any C++ code inside shared libraries is
hopeless. Non C++ works very well, non shared libraries works okay in many
cases.
latest snapshot:
ftp://ftp.cygnus.com/private/gdb/gdb-980122.tar.gz
latest branch/snapshot that will be gdb-4.17:
ftp://ftp.cygnus.com/private/gdb/gdb-4.16.85.tar.gz
if you want to subscribe to the gdb list... send to majordomo@cygnus.com,
a message with no subject just the contents:
subscribe gdb-testers you@host.domain
--
Later,
Mike Simons
Science Applications International Corporation
msimons@saic1.com 703-925-5674
next prev parent reply other threads:[~1998-02-20 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-20 8:47 D. Bernstein
1998-02-20 16:12 ` Mike Simons [this message]
1998-02-22 14:25 ` Jeffrey A Law
1998-02-22 21:25 ` Mike Simons
1998-02-22 21:43 ` Jeffrey A Law
1998-02-23 2:14 ` Mike Simons
1998-02-24 5:07 ` Jeffrey A Law
[not found] <9802230548.AA32322@rios1.watson.ibm.com>
1998-02-23 1:13 ` Mike Simons
1998-02-24 5:07 ` Jeffrey A Law
1998-02-23 15:57 Mike Stump
1998-02-24 12:51 Mike Stump
1998-02-24 12:52 ` Jeffrey A Law
1998-02-24 20:44 Mike Stump
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=199802202236.RAA00322@aura.saic1.com \
--to=msimons@saic1.com \
--cc=dan@cssgroup.com \
--cc=egcs@cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).