[Bug 44936] winedbg + gdb (remote) interaction broken due to recent commits

https://bugs.winehq.org/show_bug.cgi?id=44936

--- Comment #8 from Zebediah Figura  ---
(In reply to Julius Schwartzenberg from comment #7)
> Yes, I have the same issue then. I use these commands to let execution
> continue:
> handle SIGABRT pass nostop noprint
> handle SIGSEGV pass nostop noprint
>
> Maybe that's not the right way?

I believe that's the right way, yes. I would guess that the program intends to
catch these signals.

This is with Eclipse, right? It sounds like the debugger is working correctly
then; can you help clarify what's failing?