From: "Kévin Le Gouguec" <legouguec@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Notice when stepping into different file
Date: Fri, 02 Aug 2024 09:15:23 +0200 [thread overview]
Message-ID: <87frrne6pg.fsf@adacore.com> (raw)
In-Reply-To: <20240802055730.11865-1-tdevries@suse.de> (Tom de Vries's message of "Fri, 2 Aug 2024 07:57:30 +0200")
Tom de Vries <tdevries@suse.de> writes:
> Consider the following test-case:
> ...
> $ cat test.c
> int var;
>
> int
> foo (void)
> {
> var = 1;
> }
That puzzled me for a few seconds, until I looked at the patch:
> diff --git a/gdb/testsuite/gdb.base/step-into-other-file.c b/gdb/testsuite/gdb.base/step-into-other-file.c
> new file mode 100644
> index 00000000000..5ec7c332739
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/step-into-other-file.c
> +int var;
> +
> +int
> +foo (void)
> +{
> + var = 1;
> +#include "step-into-other-file.h"
> +}
Is this Git's core.commentChar acting up? FWIW, I've found ';' to be a
less fraught comment starter, but YMMV (indenting code samples also
works around the issue, if memory serves).
Changes themselves look good to me in principle, tho not the most
knowledgeable in that area.
Reviewed-By: Kévin Le Gouguec <legouguec@adacore.com>
next prev parent reply other threads:[~2024-08-02 7:20 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 [this message]
2024-08-05 0:44 ` Kevin Buettner
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=87frrne6pg.fsf@adacore.com \
--to=legouguec@adacore.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