Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFC: target_create_inferior that does not call proceed
Date: Tue, 24 Jan 2006 19:16:00 -0000	[thread overview]
Message-ID: <20060124191624.GA23949@nevyn.them.org> (raw)
In-Reply-To: <20060121151345.GA600@nevyn.them.org>

On Sat, Jan 21, 2006 at 10:13:46AM -0500, Daniel Jacobowitz wrote:
> > Daniel, could you please describe in some detail what happens now on
> > Posix systems when to_create_inferior is called, and in particular as
> > result of the call to `proceed'?  AFAIK, the inferior is not actually
> > running until you say "run", but your message seems to indicate
> > otherwise?
> > 
> > I need these details to decide whether your suggested change in
> > go32-nat.c is the right thing to do.

> The only call site for target_create_inferior is at the bottom of
> run_command_1.  It first creates a new inferior, and then calls
> proceed, which transitions the inferior from stopped to executing.
> prog_has_started is only set when the program is created and cleared
> when it is killed, so I think the patch is right - but I don't
> understand all the DOS-specific bits of go32-nat.c.

Hi Eli,

Was this sufficient?  Do you want to try the patch on DJGPP (since I
failed to build GDB on my local DJGPP installation)?  I'd like to check
this patch in, and I believe it's correct, but I want to make sure I
don't break go32-nat.c.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-24 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16 20:02 Daniel Jacobowitz
2006-01-16 20:59 ` Mark Kettenis
2006-01-16 21:01   ` Daniel Jacobowitz
2006-01-21 11:22 ` Eli Zaretskii
2006-01-21 15:13   ` Daniel Jacobowitz
2006-01-24 19:16     ` Daniel Jacobowitz [this message]
2006-01-24 21:45       ` Eli Zaretskii
2006-01-24 22:09         ` 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=20060124191624.GA23949@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.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