From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>,
Cary Coutant <ccoutant@google.com>
Subject: Re: [PATCH 2/6] DWARF Two Level Line Tables: dwarf2_line_debug
Date: Tue, 12 May 2015 20:39:00 -0000 [thread overview]
Message-ID: <CADPb22S+ZBgXN2h5i=SZQ-7hsZPFoQGmsSqMX5kAiafMENU4Gw@mail.gmail.com> (raw)
In-Reply-To: <83a8zi3qar.fsf@gnu.org>
On Thu, Mar 12, 2015 at 1:37 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Doug Evans <dje@google.com>
>> cc: ccoutant@google.com
>> Date: Thu, 12 Mar 2015 13:01:49 -0700
>>
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -30,6 +30,10 @@ record bts
>>
>> * New options
>>
>> +set debug dwarf2-line
>> +show debug dwarf2-line
>> + Control display of debugging info regarding DWARF line processing.
>
> This is OK.
>
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -23245,6 +23245,14 @@ The value is the number of nesting levels to print.
>> A value of zero turns off the display.
>> @item show debug dwarf2-die
>> Show the current state of DWARF2 DIE debugging.
>> +@item set debug dwarf2-line
>> +@cindex DWARF2 Line Tables
>> +Turns on or off display of debugging messages related to reading
>> +DWARF line tables. The default is 0 (off).
>> +A value of 1 provides basic information.
>> +A value greater than 1 provides more verbose information.
>> +@item show debug dwarf2-line
>> +Show the current state of DWARF2 line table debugging.
>
> This is also OK, but how about using "DWARF2" for consistency at least
> in this fragment?
Actually, I'd rather use "DWARF".
There's a lot of history/inertia here that we should really overcome
and put behind us.
We call things DWARF2 to disambiguate from DWARF1 (which no longer
exists in any useful form). dwarf2read.c should *really* be
dwarfread.c IMO (and so on for every other instance of
dwarf2/DWARF2/dw2/etc. in file names, code, docs, etc.)
> (Btw, I find this "DWARF2", "DWARF 4", "DWARF 5" thing utterly
> confusing for the reader; the truth is "DWARF version 5" etc. I wish
> we started using that throughout.)
Agreed. Where the version doesn't matter I propose using "DWARF".
(as in the above)
next prev parent reply other threads:[~2015-05-12 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 20:01 Doug Evans
2015-03-12 20:37 ` Eli Zaretskii
2015-05-12 20:39 ` Doug Evans [this message]
2015-05-13 2:44 ` Eli Zaretskii
2015-05-27 19:59 Doug Evans
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='CADPb22S+ZBgXN2h5i=SZQ-7hsZPFoQGmsSqMX5kAiafMENU4Gw@mail.gmail.com' \
--to=dje@google.com \
--cc=ccoutant@google.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