Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: MI output during program execution
Date: Tue, 04 Apr 2006 22:06:00 -0000	[thread overview]
Message-ID: <20060404220637.GA12064@nevyn.them.org> (raw)
In-Reply-To: <17458.60694.135878.624750@farnswood.snap.net.nz>

On Wed, Apr 05, 2006 at 10:03:02AM +1200, Nick Roberts wrote:
> 
> [moved from gdb-patches]
> 
> > Well I have no idea!  You didn't say what I broke.
> 
> 	* linux-nat.c (linux_ops_saved): New.
> 	(super_mourn_inferior, kill_inferior, threaded, linux_nat_ops)
> 	(child_mourn_inferior, child_wait, linux_nat_create_inferior)
> 	(linux_nat_fetch_registers, linux_nat_store_registers)
> 	(linux_nat_child_post_startup_inferior, init_linux_nat_ops): Delete.
>         ...
> 	(linux_target): Don't set to_wait, to_kill, or to_mourn_inferior.
>         ...
> 
> The async code used a heavily changed version of child_wait (in linux-nat.c).
> 
> What does the new code use in place of this procedure?

child_wait only ever worked for single-threaded executables.  Now
linux_nat_wait is used, for both single-threaded and multi-threaded
executables.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-04 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 22:03 Nick Roberts
2006-04-04 22:06 ` Daniel Jacobowitz [this message]
2006-04-26 12:36   ` Nick Roberts
2006-05-04 15:04     ` Daniel Jacobowitz
2006-05-12 11:21       ` New branch [was Re: RFC: MI output during program execution] Nick Roberts
2006-05-12 13:24         ` 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=20060404220637.GA12064@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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