From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR breakpoints/13776
Date: Tue, 28 Feb 2012 21:05:00 -0000 [thread overview]
Message-ID: <CADPb22TnfZ_BhLHL3H9s-gxRfw39mYX9XGv-LDibQvhcbWoBfw@mail.gmail.com> (raw)
In-Reply-To: <878vjmswbr.fsf@fleche.redhat.com>
On Tue, Feb 28, 2012 at 9:26 AM, Tom Tromey <tromey@redhat.com> wrote:
> I'd appreciate comments on this patch.
> [...]
> This patch fixes this problem by moving the breakpoint_init_inferior
> call earlier in generic_mourn_inferior. This causes the breakpoints to
> be marked as uninserted before they are deleted.
> [...]
> diff --git a/gdb/target.c b/gdb/target.c
> index 1f408f6..65a6c23 100644
> --- a/gdb/target.c
> +++ b/gdb/target.c
> @@ -3583,13 +3583,14 @@ generic_mourn_inferior (void)
> ptid = inferior_ptid;
> inferior_ptid = null_ptid;
>
> + breakpoint_init_inferior (inf_exited);
> +
> if (!ptid_equal (ptid, null_ptid))
> {
> int pid = ptid_get_pid (ptid);
> exit_inferior (pid);
> }
>
> - breakpoint_init_inferior (inf_exited);
> registers_changed ();
>
> reopen_exec_file ();
A comment right before the new breakpoint_init_inferior call to
explain why it lives there would be useful to future readers of the
code.
next prev parent reply other threads:[~2012-02-28 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 17:51 Tom Tromey
2012-02-28 18:27 ` Tom Tromey
2012-02-28 20:35 ` Jan Kratochvil
2012-02-28 21:05 ` Doug Evans [this message]
2012-02-29 20:07 ` Pedro Alves
2012-03-02 17:39 ` Tom Tromey
2012-03-02 18:15 ` Doug Evans
2012-03-02 19:05 ` Pedro Alves
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=CADPb22TnfZ_BhLHL3H9s-gxRfw39mYX9XGv-LDibQvhcbWoBfw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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