Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Report call site for inlined functions
Date: Tue, 11 Jul 2017 14:25:00 -0000	[thread overview]
Message-ID: <83d197jbkf.fsf@gnu.org> (raw)
In-Reply-To: <1499740601-15957-1-git-send-email-keiths@redhat.com> (message	from Keith Seitz on Mon, 10 Jul 2017 19:36:40 -0700)

> From: Keith Seitz <keiths@redhat.com>
> Date: Mon, 10 Jul 2017 19:36:40 -0700
> 
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index c167a86..58cdc1a 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -26755,6 +26755,14 @@ known.  If not known, this field is not present.
>  The line number at which this breakpoint appears, if known.
>  If not known, this field is not present.
>  
> +@item call-site-func
> +@item call-site-file
> +@item call-site-fullname
> +@item call-site-line

All but the first of these should be @itemx.

Does this warrant a NEWS entry?

OK for the documentation part, thanks.


  parent reply	other threads:[~2017-07-11 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11  2:36 Keith Seitz
2017-07-11  2:36 ` [PATCH 2/2] Report stop locations in " Keith Seitz
2017-07-18 17:16   ` Pedro Alves
2017-07-18 17:46     ` Pedro Alves
2017-10-20 19:21       ` Keith Seitz
2017-10-27 12:37         ` Pedro Alves
2017-10-30 21:18         ` Keith Seitz
2017-12-01 19:50           ` Pedro Alves
2017-10-20 19:02     ` Keith Seitz
2017-07-11 14:25 ` Eli Zaretskii [this message]
2017-07-17 19:23 ` [PATCH 1/2] Report call site for " Jan Kratochvil
2017-07-18 19:05 ` Pedro Alves
2017-10-20 18:46   ` Keith Seitz
2017-10-27 12:49     ` 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=83d197jbkf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@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