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

["mark at klomp dot org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #17 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom Tromey from comment #16)
> (In reply to Mark Wielaard from comment #15)
> > Sometimes an internal sanity check calls exit when detecting something odd
> > going on. It would be useful to catch where/when that happens with catch
> > exit.
> 
> In the implementation we're discussing, the stop would happen
> after the process already exited.  Would that still be useful?
> I can see it being useful with the TRACEEXIT implementation since
> memory would still be available... but I have trouble picturing
> using the infrun implementation.
> (Also you can "catch syscall" to catch exits, I think.  Except
> signals, but those usually cause stops anyway.)

Yes, I was hoping it would work like stop signals.
Then you simply where to see the cause of the exit.

The trouble with catch syscall is that you have to remember all the various
exit/exit_group/etc/ syscalls you need to catch for it to work properly.

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