From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Handle fork exit more gracefully in linux-fork.c
Date: Fri, 10 Mar 2006 20:08:00 -0000 [thread overview]
Message-ID: <4411D965.2020905@redhat.com> (raw)
In-Reply-To: <20060227164348.GA20931@nevyn.them.org>
Daniel Jacobowitz wrote:
> A cleanup I made while working on my next patch. I was debugging
> some checkpoint.exp failures by hand, and the most obvious thing for
> me to do was to create a checkpoint, let the current one exit, and
> then continue the previous checkpoint - but as soon as I did this
> it crashed with corrupted register state.
>
> We weren't restoring the saved registers in linux_fork_mourn_inferior.
> And we were somehow clobbering the previous registers. Moving
> some bits from the explicit context-switch code into the restore-a-fork
> routine fixed all that.
Answered my own questions. Yes, this looks fine.
By the way, when you include your .sig *before* the patch,
thunderbird won't include the patch in the reply. ;-(
next prev parent reply other threads:[~2006-03-10 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 19:28 Daniel Jacobowitz
2006-03-10 20:08 ` Michael Snyder [this message]
2006-03-24 23:08 ` Daniel Jacobowitz
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=4411D965.2020905@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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