public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lancelot SIX <lancelot.six@amd.com>
Cc: gdb-patches@sourceware.org, lsix@lancelotsix.com
Subject: Re: [PATCH v2 2/2] gdb: Add support for DW_LNS_set_prologue_end in line-table
Date: Wed, 30 Mar 2022 15:26:31 +0300	[thread overview]
Message-ID: <838rsr8w3s.fsf@gnu.org> (raw)
In-Reply-To: <20220330093458.148497-3-lancelot.six@amd.com> (message from Lancelot SIX via Gdb-patches on Wed, 30 Mar 2022 10:34:58 +0100)

> Date: Wed, 30 Mar 2022 10:34:58 +0100
> From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
> Cc: lsix@lancelotsix.com, Lancelot SIX <lancelot.six@amd.com>
> 
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -8,6 +8,17 @@
>  * Remove support for building against Python 2, it is now only possible to
>    build GDB against Python 3.
>  
> +* GDB now honours the DWARF prologue_end line-table entry flag the compiler can
> +  emit to indicate where a breakpoint should be placed to break in a function
> +  past its prologue.
> +
> +* Changed commands
> +
> +maintenance info line-table
> +  Add a PROLOGUE-END column to the output which indicates that an
> +  entry corresponds to an address where a breakpoint should be placed
> +  to be at the first instruction past a function's prologue.
> +
>  * Python API
>  

This part is OK.

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -19794,6 +19794,33 @@ line 1574.
>  List the @code{struct linetable} from all @code{struct symtab}
>  instances whose name matches @var{regexp}.  If @var{regexp} is not
>  given, list the @code{struct linetable} from all @code{struct symtab}.
> +For example:
> +
> +@smallexample
> +(@value{GDBP}) maint info line-table
> +objfile: /home/gnu/build/a.out ((struct objfile *) 0x6120000e0d40)
> +compunit_symtab: simple.cpp ((struct compunit_symtab *) 0x6210000ff450)
> +symtab: /home/gnu/src/simple.cpp ((struct symtab *) 0x6210000ff4d0)
> +linetable: ((struct linetable *) 0x62100012b760):
> +INDEX  LINE   ADDRESS            IS-STMT PROLOGUE-END
> +0      3      0x0000000000401110 Y
> +1      4      0x0000000000401114 Y       Y
> +2      9      0x0000000000401120 Y
> +3      10     0x0000000000401124 Y       Y
> +4      10     0x0000000000401129
> +5      15     0x0000000000401130 Y
> +6      16     0x0000000000401134 Y       Y
> +7      16     0x0000000000401139
> +8      21     0x0000000000401140 Y
> +9      22     0x000000000040114f Y       Y
> +10     22     0x0000000000401154
> +11     END    0x000000000040115a Y
> +@end smallexample
> +@noindent

This is also OK, but please fix this:

> +The @samp{IS-STMT} column indicates if the address is a recommended breakpoint
> +location to represent a line or a statement.  The @samp{PROLOGUE-END} column
> +indicates that a given address is an adequate to place a breakpoint at the
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That should be "is an adequate place to set a breakpoint".

Thanks.

  reply	other threads:[~2022-03-30 12:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  9:34 [PATCH v2 0/2] Add support for DWARF's prologue_end flag " Lancelot SIX
2022-03-30  9:34 ` [PATCH v2 1/2] gdb/buildsym: Line record use a record flag Lancelot SIX
2022-03-31  9:57   ` Pedro Alves
2022-03-31 10:18     ` Pedro Alves
2022-03-31 10:04   ` Pedro Alves
2022-03-30  9:34 ` [PATCH v2 2/2] gdb: Add support for DW_LNS_set_prologue_end in line-table Lancelot SIX
2022-03-30 12:26   ` Eli Zaretskii [this message]
2022-03-30 12:54     ` Lancelot SIX
2022-03-31 10:17   ` Pedro Alves

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=838rsr8w3s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lancelot.six@amd.com \
    --cc=lsix@lancelotsix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).