public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26594] 'info line' does not print all corresponding addresses
Date: Thu, 10 Sep 2020 13:08:57 +0000	[thread overview]
Message-ID: <bug-26594-4717-mShcom3Y6m@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26594-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26594

--- Comment #1 from trass3r <trass3r at gmail dot com> ---
Indeed the following patch using the same flags as the jump or breakpoint
commands yields expected results:

diff --git a/gdb/source.c b/gdb/source.c
index 0c2b5a4f83..6e6705779f 100644
--- a/gdb/source.c
+++ b/gdb/source.c
@@ -1463,7 +1463,7 @@ info_line_command (const char *arg, int from_tty)
   else
     {
       decoded_sals = decode_line_with_last_displayed (arg,
-                                                     DECODE_LINE_LIST_MODE);
+                                                    
DECODE_LINE_FUNFIRSTLINE);
       sals = decoded_sals;

       dont_repeat ();


$ i line test2.cpp:21
Line 22 of "test2.cpp" starts at address 0x55f4d74da3ec <foo<int>(int)+15> and
ends at 0x55f4d74da3f1 <foo<int>(int)+20>.
Line 22 of "test2.cpp" starts at address 0x55f4d74da407 <foo<float>(float)+17>
and ends at 0x55f4d74da40c <foo<float>(float)+22>.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-09-10 13:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 22:23 [Bug gdb/26594] New: " trass3r at gmail dot com
2020-09-10 13:08 ` trass3r at gmail dot com [this message]
2024-04-04 17:18 ` [Bug gdb/26594] " tromey at sourceware dot org
2024-04-04 18:54 ` trass3r at gmail dot com

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=bug-26594-4717-mShcom3Y6m@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).