Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Gianni Mariani" <gianni@mariani.ws>
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: <gdb@sourceware.cygnus.com>
Subject: RE: Why does C++ support in GDB suck so badly ?
Date: Thu, 06 Sep 2001 00:03:00 -0000	[thread overview]
Message-ID: <NEBBJABEOLOOJHHPENFDGEKJCBAA.gianni@mariani.ws> (raw)
In-Reply-To: <3B971A15.9000100@cygnus.com>

Andrew, thanks to the pointer to the thread.

So it seems there are 2 main underlying problems:

1. Dwarf 2 reader support is less than optimal
2. Proper name space support is lacking

I would have to agree that just being able to correctly
print a data structure goes a long way.

Is anyone actively managing the C++ bugs ?

What kind of help does the GDB team need ?

I'm willing to help.

G

-----Original Message-----
From: Andrew Cagney [ mailto:ac131313@cygnus.com ]
Sent: Wednesday, September 05, 2001 11:39 PM
To: Gianni Mariani
Cc: gdb@sourceware.cygnus.com
Subject: Re: Why does C++ support in GDB suck so badly ?


 > It is really bad that you can't examine a simple data structure - because
 > of "virtual baseclass botch" or "Value can't be converted to integer
" messages.
 >
 > Are there alternatives ?
 >
 > I'm willing to help - but my reseach tells me that's going to be useless:
 > http://gcc.gnu.org/ml/gcc/2001-03/msg00475.html

Always take any thing you read with a pinch of salt.  That includes this
e-mail.

 > Is gdb so bad now that it needs to be thrown out and started again -
in C++ ?

Some how, i suspect that would be a bad move.  When it comes down to it,
GDB's basic architecture must be ok - it would have to be to last 15 years!

The real problem is that there are a number of C++ bugs, some some of
which are complex - check this mailing list for MichaelC's summary.

I don't think the complexity is comming from gdb's c++ support code,
rather it is comming from changes needed to core core-gdb.  It is like
hurding wild cattle through a cattle dip.  You can't get all the
required changes through in a single hit, however with a little
organization, some help, and some hard work, you'll soon get things
moving in the right direction.

 > Lack of response to my query on August 21st also shows a real lack of
interest
 > from the current gdb team so I'm worried.
 >
 > Will someone on the gdb team please let us know what your plans are
to address
 > the lack of C++ support - even if you have none .

Keep in mind that people, having learnt from past mistakes, tend to only
say something when they have both come up with a prototype of an idea
and are willing/able to follow it through to a final implementation.

See the thread:

http://sources.redhat.com/ml/gdb/2001-06/msg00219.html

I think some people have worn themselves out trying to wressle a very
large bull called ``name space''.  The last comment I saw, suggested
that rewriting the dwarf2 reader is probably overkill.

If I remember right, this, and other smaller problems are always
available for the taking.

Got your GPL assignment in order?

Andrew


  reply	other threads:[~2001-09-06  0:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02 17:58 Gianni Mariani
2001-09-05 23:39 ` Andrew Cagney
2001-09-06  0:03   ` Gianni Mariani [this message]
2001-09-06 12:04 ` Jim Blandy
2001-09-06 13:12   ` Daniel Berlin

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=NEBBJABEOLOOJHHPENFDGEKJCBAA.gianni@mariani.ws \
    --to=gianni@mariani.ws \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sourceware.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