From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] inadvertent language switch during breakpoint_re_set_one
Date: Fri, 01 Jun 2018 12:42:00 -0000 [thread overview]
Message-ID: <5d0da8ec-624d-24ee-85d4-8b2dc6f6349f@redhat.com> (raw)
In-Reply-To: <20180510204034.uxpqi3uuvvmk7koc@adacore.com>
LGTM. Could nits below.
On 05/10/2018 09:40 PM, Joel Brobecker wrote:
> --- a/gdb/breakpoint.c
> +++ b/gdb/breakpoint.c
> @@ -13881,6 +13881,19 @@ breakpoint_re_set (void)
> scoped_restore save_input_radix = make_scoped_restore (&input_radix);
> scoped_restore_current_pspace_and_thread restore_pspace_thread;
>
> + /* breakpoint_re_set_one sets the current_language to the language
> + of the breakpoint it is resetting (see prepare_re_set_context)
> + before re-evaluating the breakpoint's location. This change can
> + unfortunately get undone by accident if the language_mode is set
> + to auto, and we either switch frames, or more likely in this context,
> + we select the current frame.
> +
> + We prevent this by temporarily turning the language_mode to
> + language_mode_manual. We we restore it once all breakpoints
Double "We we".
> +gdb_run_cmd
> +gdb_test "" \
> + "Breakpoint $decimal, a \\(\\).*" \
> + "Run until breakpoint at a'address"
Lowercase "run".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-06-01 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 18:42 Joel Brobecker
2018-05-10 18:58 ` Sergio Durigan Junior
2018-05-10 19:26 ` Joel Brobecker
2018-05-10 19:08 ` Keith Seitz
2018-05-10 19:21 ` Joel Brobecker
2018-05-10 19:35 ` Keith Seitz
2018-05-10 19:29 ` Tom Tromey
2018-05-10 20:59 ` Joel Brobecker
2018-05-31 0:02 ` Joel Brobecker
2018-06-01 12:42 ` Pedro Alves [this message]
2018-06-01 16:39 ` Joel Brobecker
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=5d0da8ec-624d-24ee-85d4-8b2dc6f6349f@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).