From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Luis Machado <luis.machado@arm.com>
Subject: Re: [PATCH] [gdb/testsuite] Fix linespec ambiguity in gdb.base/longjmp.exp
Date: Fri, 10 Feb 2023 07:36:57 -0700 [thread overview]
Message-ID: <87a61lziwm.fsf@tromey.com> (raw)
In-Reply-To: <20230210105749.2893-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Fri, 10 Feb 2023 11:57:49 +0100")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Due to the KFAIL PR, gdb stopped in __libc_siglongjmp, and because of presence
Tom> of debug info, the "current source file" becomes glibc's ./setjmp/longjmp.c.
Tom> Consequently, setting the breakpoint fails.
Tom> Fix this by adding a $subdir/$srcfile: prefix to the breakpoint linespecs.
Makes sense to me.
Reviewed-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-02-10 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 10:57 Tom de Vries
2023-02-10 14:36 ` Tom Tromey [this message]
2023-02-10 14:58 ` Luis Machado
2023-02-10 15:00 ` Tom de Vries
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=87a61lziwm.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).