Chris Johns wrote:
> Hello Earnie,
> I have been looking into this and I need some help.
Perhaps this search might be useful?
> We have a couple of cases where this happens.
> The first is console app. Here we tell the process to be debugged to
> create a separate console. This is fine as a Ctrl-Break is transfered to
> GDB via the WaitForDebugEvent Win32 call. If we run the child process in
> the same console as GDB the Ctrl-BREAK hits gdb rather than the child
> and this exits GDB.
Perhaps you need this:
> Note, the binary I uploaded does not open a new console window.
> The second is a Windows app (linked with -mwindows) and so no console.
> Here we would like to catch the Ctrl C/break event in the GDB window.
> This is easy, how-ever dealing with the event is not, well for me that
> is. The event handler is called on a new thread. The wait for debug
> event thread is still waiting and the child app is still running.
> I cannot find a system call that would suspend, or stop or even raise an
> SEH exception in the child to wake it up. The DebugBreakProcess looked
> like the correct things, how-ever it is only XP and friends.
> Do you have any idea on how to do this ?
No, so I've CCed the list.
Powered by SourceForge <http://sourceforge.net/projects/mingw>