public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, ccoutant@google.com
Subject: Re: [PATCH 2/6] DWARF Two Level Line Tables: dwarf2_line_debug
Date: Thu, 12 Mar 2015 20:37:00 -0000	[thread overview]
Message-ID: <83a8zi3qar.fsf@gnu.org> (raw)
In-Reply-To: <yjt28uf27zo2.fsf@ruffy.mtv.corp.google.com>

> 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?

(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.)

Thanks.

  reply	other threads:[~2015-03-12 20:37 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 [this message]
2015-05-12 20:39   ` Doug Evans
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=83a8zi3qar.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ccoutant@google.com \
    --cc=dje@google.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).