From: Daniel Berlin <dan@dberlin.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@redhat.com>, <gdb@sources.redhat.com>,
Benjamin Kosnik <bkoz@redhat.com>
Subject: Re: C++ nested classes, namespaces, structs, and compound statements
Date: Sat, 06 Apr 2002 07:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0204061055480.26470-100000@dberlin.org> (raw)
In-Reply-To: <3CAF06B6.8030809@cygnus.com>
On Sat, 6 Apr 2002, Andrew Cagney wrote:
> > At the moment, GDB doesn't handle C++ namespaces or nested classes
> > very well. I have a general idea of how we could address these
> > limitations, which I'd like to put up for shredding M-DEL discussion.
> >
> > Let me admit up front that I don't really know C++, so I may be saying
> > stupid things. Please set me straight if you notice something.
> >
> > In C, structs are essentially lists of member names, types, and
> > locations (offsets from the structure's base address):
> >
> > struct S { int x; char y; struct T t; }
> >
> > (Unions are just the same, except that the offsets are all zero. That
> > relationship carries through the entire discussion here, so I'm not
> > going to talk about unions any more.)
> >
> > If you think about it just right (or just wrong), this is really very
> > similar to the set of local variables associated with a compound
> > statement:
>
> I'm very interested in hearing about what ACT did for Ada. As far as I
> know Ada, with its packages et.al. has a very similar problem and,
> potentially, working code.
The last time I scanned the Ada changes (a few days ago), they hadn't
handled this problem at all.
Probably because gcc doesn't produce module/packages/etc debug info for
Ada.
--Dan
>
> Andrew
>
next prev parent reply other threads:[~2002-04-06 15:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 20:42 Jim Blandy
2002-04-05 22:05 ` Daniel Berlin
2002-04-05 22:34 ` Daniel Jacobowitz
2002-04-05 23:49 ` Daniel Berlin
2002-04-06 7:18 ` Dan Kegel
2002-04-06 9:26 ` Gianni Mariani
2002-04-06 11:57 ` Daniel Berlin
2002-04-08 17:24 ` Jim Blandy
2002-04-08 17:03 ` Jim Blandy
2002-04-08 18:59 ` Daniel Jacobowitz
2002-04-09 18:35 ` Jim Blandy
2002-04-09 20:56 ` Daniel Jacobowitz
2002-04-12 15:08 ` Jim Blandy
2002-04-12 16:32 ` Daniel Jacobowitz
2002-04-08 17:19 ` Jim Blandy
2002-04-08 18:49 ` Daniel Jacobowitz
2002-04-10 10:31 ` Jim Blandy
2002-04-10 12:08 ` Daniel Jacobowitz
2002-04-12 13:58 ` Jim Blandy
2002-04-12 16:56 ` Daniel Jacobowitz
2002-04-16 12:08 ` Jim Blandy
2002-04-16 14:01 ` Daniel Jacobowitz
2002-04-16 14:52 ` Jim Blandy
2002-04-16 14:58 ` Daniel Jacobowitz
2002-04-06 6:31 ` Andrew Cagney
2002-04-06 7:58 ` Daniel Berlin [this message]
2002-04-08 0:59 ` Joel Brobecker
2002-04-08 2:01 ` Doubt in GDB SathisKanna k
2002-04-06 8:49 ` C++ nested classes, namespaces, structs, and compound statements Per Bothner
2002-04-08 16:29 ` Jim Blandy
2002-04-08 16:48 ` Daniel Jacobowitz
2002-04-09 6:55 ` Petr Sorfa
2002-04-10 10:34 ` Jim Blandy
2002-04-10 12:31 ` Daniel Berlin
2002-04-10 12:53 ` Petr Sorfa
2002-04-05 22:02 Michael Elizabeth Chastain
2002-04-05 22:13 ` Daniel Berlin
2002-04-05 22:30 ` 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=Pine.LNX.4.44.0204061055480.26470-100000@dberlin.org \
--to=dan@dberlin.org \
--cc=ac131313@cygnus.com \
--cc=bkoz@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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