Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: manual updates for c++
Date: Fri, 11 Nov 2011 15:00:00 -0000	[thread overview]
Message-ID: <m3lirmu2ku.fsf@fleche.redhat.com> (raw)
In-Reply-To: <838vnngj7b.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Nov	2011 10:24:40 +0200")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> Both -gstabs+ and -gdwarf-2 are obsolete nowadays

Eli> On most platforms, but not on all of them.  It's true that -gdwarf-2
Eli> is the default, though.

No, -gdwarf-3 is the default.  Someday it will be -gdwarf-4.  -gdwarf-2
really is obsolete, DWARF 2 is quite ancient and there have been many
important additions since then.

-gstabs+ ... I don't know as much about stabs.  My impression is that
they don't handle C++ very well.  Certainly on the GCC side nobody puts
any work into them at all, and very little work in GDB.

So, I think that sentence remains true.  Perhaps it is untrue on
platforms which are themselves obsolete.

>> +                                               Starting with version
>> +4.7, @value{NGCC} can emit macro information in a more compact format.

Eli> Why is this part important to a GDB user?

A previous sentence mentions that the information is large.  Assuming
that this earlier sentence provides any value to the GDB user,
mentioning that the problem can be ameliorated also seems appropriate.

>> +     Recent versions of @value{NGCC} support @option{-gdwarf-3}
>> +@option{-gdwarf-4};

Eli> Should there be an "and" between the two option names?  They are
Eli> orthogonal, right?

Yes.

Tom


  reply	other threads:[~2011-11-11 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 18:45 Tom Tromey
2011-11-11  8:27 ` Eli Zaretskii
2011-11-11 15:00   ` Tom Tromey [this message]
2011-11-11 15:47     ` Eli Zaretskii
2011-11-11 16:27       ` Tom Tromey
2011-11-11 16:51         ` Eli Zaretskii
2011-11-27 20:46     ` Jan Kratochvil

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=m3lirmu2ku.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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