This is the mail archive of the
mailing list for the GDB project.
Re: RFC: MI output during program execution
- From: Daniel Jacobowitz <drow at false dot org>
- To: Nick Roberts <nickrob at snap dot net dot nz>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 4 Apr 2006 18:06:37 -0400
- Subject: Re: RFC: MI output during program execution
- References: <firstname.lastname@example.org>
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