From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [RFC] [gdb] Stop on undetermined longjmp target during next
Date: Thu, 15 Dec 2022 14:31:33 -0700 [thread overview]
Message-ID: <878rj8cq16.fsf@tromey.com> (raw)
In-Reply-To: <20221208113140.1231-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Thu, 8 Dec 2022 12:31:40 +0100")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> --- a/gdb/infrun.c
Tom> +++ b/gdb/infrun.c
Tom> @@ -6650,7 +6650,8 @@ process_event_stop_test (struct execution_control_state *ecs)
Tom> {
Tom> infrun_debug_printf ("BPSTAT_WHAT_SET_LONGJMP_RESUME "
Tom> "(!gdbarch_get_longjmp_target)");
Tom> - keep_going (ecs);
Tom> + warning (_("GDB can't determine the longjmp target"));
Tom> + end_stepping_range (ecs);
I'm not really an infrun expert, so I haven't replied to this.
But, FWIW, I think the idea makes sense.
Tom
prev parent reply other threads:[~2022-12-15 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:31 Tom de Vries
2022-12-08 12:02 ` Andreas Schwab
2022-12-08 13:33 ` Tom de Vries
2022-12-15 21:31 ` Tom Tromey [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=878rj8cq16.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--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).