[Bug threads/19471] unexpected stop in multi-inferior debugging

["tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19471

--- Comment #11 from Tom Tromey <tromey at sourceware dot org> ---
> IWBN if we had some sort of "catch inferior-exit" / "catch exit" catchpoint,
which you'd use to stop when an inferior exits.  If we had that, switching to
not stopping by default would be an even easier sell.

I started one once.  It's in my github, on the catch-exit branch.

It worked by using PTRACE_O_TRACEEXIT, so not exactly the same thing.
I suppose on systems without that, it could fall back to target-waitkind-based
stops.

It would need quite a bit of work now.  And, I never wrote the gdbserver
or remote protocol parts.

> You should probably be calling resume or keep_going.

I tried what you suggested and it works, but I don't really know
if it's correct or even close.

-- 
You are receiving this mail because:
You are on the CC list for the bug.