From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] remote-mips.c: Fix bit rot associated with the inferior's state
Date: Fri, 05 Mar 2010 16:26:00 -0000 [thread overview]
Message-ID: <20100305092637.16a2c569@redhat.com> (raw)
In-Reply-To: <201003051553.46571.pedro@codesourcery.com>
On Fri, 5 Mar 2010 15:53:46 +0000
Pedro Alves <pedro@codesourcery.com> wrote:
> > I tried setting attach_flag in the inferior and making mips_kill throw
> > an error, but that messes up gdb.base/opaque.exp.
[...]
>
> I'd call it a test bug to be trying to kill on such
> configuration...
I think you might be right since gdb.base/opaque.exp is one of the few
tests for which this is a problem. (It might even be the only test for
which this is a problem.)
> > * remote-mips.c (gdbthread.h): Include.
> > (remote_mips_ptid): Declare.
> > (mips_error): Only mourn the inferior when inferior_ptid is non-null.
> > (common_open): Set inferior_ptid, add it as an inferior, and
> > as a thread too. Delete FIXME comment regarding start_remote().
> > (mips_close): Invoke generic_mourn_inferior().
> > (mips_kill): Make sure that target_mourn_inferior is invoked.
> > (mips_mourn_inferior): Don't invoke generic_mourn_inferior, as
> > it's now invoked from mips_close().
> > (mips_load): Don't null out inferior_ptid. Don't call
> > clear_symtab_users().
> > (mips_thread_alive, mips_pid_to_str): New functions.
> > (_initialize_remote_mips): Initialize remote_mips_ptid. Initialize
> > to_thread_alive and to_pid_to_str operations.
>
> Looks good to me. Thanks.
I've committed this patch. Thanks again for your reviews.
Kevin
prev parent reply other threads:[~2010-03-05 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 0:25 Kevin Buettner
2010-03-02 23:09 ` Kevin Buettner
2010-03-02 23:37 ` Pedro Alves
2010-03-03 23:44 ` Kevin Buettner
2010-03-04 0:33 ` Pedro Alves
2010-03-04 23:33 ` Kevin Buettner
2010-03-05 15:53 ` Pedro Alves
2010-03-05 16:26 ` Kevin Buettner [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=20100305092637.16a2c569@redhat.com \
--to=kevinb@redhat.com \
--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