Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: eliz@is.elta.co.il
Cc: gdb@sources.redhat.com, sassi@uni.de
Subject: Re: GDB C++ support
Date: Tue, 15 Jan 2002 05:57:00 -0000	[thread overview]
Message-ID: <200201151357.HAA17255@duracef.shout.net> (raw)

Sheesh, Eli.  Guido asked:

gs> So my question would be, how far the work on support for C++ and gcc 3.x
gs> went as of now, and if one could expect some solution to this problem in the
gs> near future?
gs> 
gs> It just confuses me, that the development of gcc and gdb seems so
gs> asynchronous, and a compiler suite, as elegant as it may be, withers away if
gs> it lacks usable debugging support.

And that's what I answered, especially the second part.

eli> Do you (or someone else) happen to know whether v5.1 solves some or
eli> all of the specific problems Guido described in his message?  If not,
eli> he has no reason to try GDB 5.1, does he?

Well, gdb 5.0 was released more than a year before gcc 3.0, and gdb 5.1
was released more than 5 months after gcc 3.0.  That's a good reason
to expect that gdb 5.1 will work a lot better than gdb 5.0 when the
target program is compiled with gcc 3.0.3.

I don't have gcc 3.0.3 installed yet (I wish I did).  I don't have
djgpp 2.03 installed (I probably never will).  And I don't have time
to chase after user bug reports with incomplete source code and gdb 5.0.

Michael C


             reply	other threads:[~2002-01-15 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15  5:57 Michael Elizabeth Chastain [this message]
2002-01-15  9:15 ` Eli Zaretskii
     [not found] <1011102697.16058.ezmlm@sources.redhat.com>
2002-01-15 13:08 ` Jim Ingham
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15  9:48 Michael Elizabeth Chastain
2002-01-15 10:00 ` Eli Zaretskii
2002-01-15 10:14 ` Daniel Jacobowitz
2002-01-14 10:40 Michael Elizabeth Chastain
2002-01-14 23:43 ` Eli Zaretskii
2002-01-14 10:25 Guido S.

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=200201151357.HAA17255@duracef.shout.net \
    --to=mec@shout.net \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=sassi@uni.de \
    /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