From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Notice when stepping into different file
Date: Sun, 4 Aug 2024 17:44:27 -0700 [thread overview]
Message-ID: <20240804174427.01d03a26@f40-zbm-amd> (raw)
In-Reply-To: <20240802055730.11865-1-tdevries@suse.de>
On Fri, 2 Aug 2024 07:57:30 +0200
Tom de Vries <tdevries@suse.de> wrote:
> Instead, change the behaviour of "print frame-info" == auto to also use
> source-and-location when stepping into another file, which gets us:
> ...
> (gdb) n
> foo () at test.h:1
> 1 return 1;
> ...
LGTM. (Aside from git eating the #include line in the commit remarks.)
Reviewed-by: Kevin Buettner <kevinb@redhat.com>
prev parent reply other threads:[~2024-08-05 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 5:57 Tom de Vries
2024-08-02 7:15 ` Kévin Le Gouguec
2024-08-05 0:44 ` Kevin Buettner [this message]
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=20240804174427.01d03a26@f40-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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