Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] fix crash when rerunning programs in non-stop mode
Date: Fri, 27 Mar 2009 02:18:00 -0000	[thread overview]
Message-ID: <200903270123.19171.pedro@codesourcery.com> (raw)
In-Reply-To: <20090327004601.576E41C74E3@localhost>

On Friday 27 March 2009 00:46:01, Doug Evans wrote:

> One problem is that calling is_exited is problematic if
> ! target_has_execution (this one I'm tripping over).

Ooops.  FYI, I'm going to elimiminate those particular
target_has_execution checks in a near future.

> Another problem is if tp == NULL, then old->inferior_ptid
> is restored (this is just an observation).

Ooops 2.  Thank you for fixing this.

> 
> This patch reverses the sense of what's being tested,
> i.e. check for whether old->inferior_ptid restorable
> instead of whether it's dead.
> 
> Ok to check in?

Ok.  Thanks.

> Included is a testcase to exercise the problem.

Thanks, that's much appreciated.

> 2009-03-26  Doug Evans  <dje@google.com>
>
> 	* thread.c (do_restore_current_thread_cleanup): Redo test for
> 	whether to restore old->inferior_ptid.
> 
> 	* gdb.mi/mi-nonstop-exit.exp: New file.
> 	* gdb.mi/non-stop-exit.c: New file.

Remember to put the test logs in testsuite/ChangeLog.

I'll adjust this new test to be able run it against gdbserver
once this is in:

 http://sourceware.org/ml/gdb-patches/2009-03/msg00587.html

-- 
Pedro Alves


      reply	other threads:[~2009-03-27  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  1:23 Doug Evans
2009-03-27  2:18 ` Pedro Alves [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=200903270123.19171.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dje@google.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