From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't print symbol definition's line number in rbreak output
Date: Mon, 16 Apr 2018 19:01:00 -0000 [thread overview]
Message-ID: <e527a164-3aae-8b83-7671-067c5a02eff7@redhat.com> (raw)
In-Reply-To: <m3sh7v3sag.fsf@oc1027705133.ibm.com>
On 04/16/2018 07:44 PM, Andreas Arnez wrote:
> This commit:
>
> b744723f57 -- Show line numbers in output for "info var/func/type"
>
> added the symbol definition's line number to the output of certain GDB
> commands. It also changes the `rbreak' command's output, although it
> shouldn't. This is fixed.
Could you update this to include an example of before/after gdb
output in the commit log?
Is this a regression in 8.1?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-16 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 18:44 Andreas Arnez
2018-04-16 19:01 ` Pedro Alves [this message]
2018-04-17 12:28 ` Andreas Arnez
2018-04-17 15:18 ` Pedro Alves
2018-04-17 16:39 ` Andreas Arnez
2018-04-17 16:56 ` Pedro Alves
2018-04-17 17:33 ` Andreas Arnez
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=e527a164-3aae-8b83-7671-067c5a02eff7@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.ibm.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).