Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [patch/rfc] mention C++ support in NEWS
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <yf2y8q0z57x.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <6654-Wed11Feb2004213143+0200-eliz@elta.co.il> (Eli Zaretskii's message of "Wed, 11 Feb 2004 21:31:44 +0200")

On Wed, 11 Feb 2004 21:31:44 +0200, "Eli Zaretskii" <eliz@elta.co.il> said:
>> From: David Carlton <carlton@kealia.com>
>> Date: Wed, 11 Feb 2004 10:15:27 -0800

>> +* C++ nested types and namespaces
>> +
>> +GDB's support for nested types and namespaces in C++ has been
>> +improved.  We recommend that you use the DWARF 2 debugging format to
>> +get the full benefit from this; this is the default for recent
>> +versions of GCC on most platforms.
>> +

> IMHO, this text is okay, but perhaps it will sound much more useful if
> you add some examples of situations where GDB previously didn't work,
> and now does.

That's a good point.  How about:

  GDB's support for nested types and namespaces in C++ has been
  improved, especially if you use the DWARF 2 debugging format.  (This
  is the default for recent versions of GCC on most platforms.)
  Specifically, if you have a class "Inner" defined within a class or
  namespace "Outer", then GDB realizes that the class's name is
  "Outer::Inner", not simply "Inner".  This should greatly reduce the
  frequency of complaints about not finding RTTI symbols.  In
  addition, if you are stopped at inside of a function defined within
  a namespace, GDB modifies its name lookup accordingly.

I'm still not entirely thrilled with it, especially that last
sentence; I don't want to go into _too_ many details, but I'm not sure
I've found the right balance.

I'm also trying to think of what else has changed - the patches have
been long enough that I would think I'd be able to point to more
features, but I guess it really is the case that fixing names of types
and teaching GDB about namespaces simply required a lot of
infrastructure changes...

David Carlton
carlton@kealia.com


WARNING: multiple messages have this Message-ID
From: David Carlton <carlton@kealia.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [patch/rfc] mention C++ support in NEWS
Date: Wed, 17 Mar 2004 00:29:00 -0000	[thread overview]
Message-ID: <yf2y8q0z57x.fsf@hawaii.kealia.com> (raw)
Message-ID: <20040317002900.5Rw9JXVfzSMfgeEy4_2oDQ4nQy2-fQPZh4Pd23LIVBY@z> (raw)
In-Reply-To: <6654-Wed11Feb2004213143+0200-eliz@elta.co.il> (Eli Zaretskii's message of "Wed, 11 Feb 2004 21:31:44 +0200")

On Wed, 11 Feb 2004 21:31:44 +0200, "Eli Zaretskii" <eliz@elta.co.il> said:
>> From: David Carlton <carlton@kealia.com>
>> Date: Wed, 11 Feb 2004 10:15:27 -0800

>> +* C++ nested types and namespaces
>> +
>> +GDB's support for nested types and namespaces in C++ has been
>> +improved.  We recommend that you use the DWARF 2 debugging format to
>> +get the full benefit from this; this is the default for recent
>> +versions of GCC on most platforms.
>> +

> IMHO, this text is okay, but perhaps it will sound much more useful if
> you add some examples of situations where GDB previously didn't work,
> and now does.

That's a good point.  How about:

  GDB's support for nested types and namespaces in C++ has been
  improved, especially if you use the DWARF 2 debugging format.  (This
  is the default for recent versions of GCC on most platforms.)
  Specifically, if you have a class "Inner" defined within a class or
  namespace "Outer", then GDB realizes that the class's name is
  "Outer::Inner", not simply "Inner".  This should greatly reduce the
  frequency of complaints about not finding RTTI symbols.  In
  addition, if you are stopped at inside of a function defined within
  a namespace, GDB modifies its name lookup accordingly.

I'm still not entirely thrilled with it, especially that last
sentence; I don't want to go into _too_ many details, but I'm not sure
I've found the right balance.

I'm also trying to think of what else has changed - the patches have
been long enough that I would think I'd be able to point to more
features, but I guess it really is the case that fixing names of types
and teaching GDB about namespaces simply required a lot of
infrastructure changes...

David Carlton
carlton@kealia.com


  parent reply	other threads:[~2004-03-17  0:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 18:15 David Carlton
2004-02-11 19:31 ` Eli Zaretskii
2004-02-16 19:44   ` Daniel Jacobowitz
2004-03-19  0:09   ` David Carlton [this message]
2004-03-17  0:29     ` David Carlton
2004-03-19  0:09     ` Eli Zaretskii
2004-03-17  6:11       ` Eli Zaretskii
2004-03-17 17:32       ` Daniel Jacobowitz
2004-03-19  0:09         ` David Carlton
2004-03-17 17:39           ` David Carlton
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-17  1:29 Michael Elizabeth Chastain
2004-03-19  0:09 ` Michael Elizabeth Chastain

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=yf2y8q0z57x.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=drow@mvista.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.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