Re: Some more multi-fork fixes

[Daniel Jacobowitz <drow@false.org>]

On Fri, Jan 27, 2006 at 12:01:02PM -0800, Michael Snyder wrote:
> >Some other problems I noticed, but did not fix:
> >
> >The "follow child, print pids" test is victim of a race condition; 
> >sometimes
> >the "$pid done" printout from the inferior will be interleaved with the GDB
> >output, causing expect to mark the test as a failure.
> >
> >delete-fork really ought to call waitpid after deleting the fork; otherwise
> >the process lives on as a zombie.
> 
> That's fine with me too.

Well, I'd been sort of hoping that you (as the developer who
contributed this huge pile of new code) would take care of its
reported bugs.

I'm up against a bit of a brick wall at the moment.  I've got
patches in my source tree to unify the single-threaded and
multi-threaded code in the Linux native layer into a single
combined target.  But since this is an inherently single-threaded
operation the multi-threaded code totally falls down - switching
forks doesn't preserve things like the LWP list, leading to
messy timeouts.  I'm going to find some minimally painful
way to make the two of them talk to each other.

-- 
Daniel Jacobowitz
CodeSourcery