Re: GDB Ctrl-C Interrupt Fails WORKAROUND

2006-06-15 Thread Kyle McKay
duced programs. Apparently you did not see my previous comments about this: On 15 Jun 2006 10:38:57 -0700, Kyle McKay wrote: Now if you have such a program compiled with the m$ compiler for which you do not have the source and such a program is loading a DLL plugin built with cygwin that y

Re: GDB Ctrl-C Interrupt Fails WORKAROUND

2006-06-15 Thread Kyle McKay
On 15 Jun 2006 11:04:56 -0400, Christopher Faylor wrote: >Lacking the ability to interrupt a running program severely limits >gdb's usefulness. Fortunately there's a workaround available. Yep. Use a console window. Maybe I haven't been clear. THIS DOES NOT WORK. Compile the below hellowin.

Re: GDB Ctrl-C Interrupt Fails WORKAROUND

2006-06-15 Thread Kyle McKay
On 15 Jun 2006 at 00:44:05 -0400 Christopher Faylor wrote: On Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote: >If you have ever tried to interrupt a program running under cygwin >gdb, you have probably experienced some frustration. Especially if >the program was built with -m

GDB Ctrl-C Interrupt Fails WORKAROUND

2006-06-14 Thread Kyle McKay
If you have ever tried to interrupt a program running under cygwin gdb, you have probably experienced some frustration. Especially if the program was built with -mno-cygwin. Here is a workaround. You've probably discovered that pressing Ctrl-C in the gdb window/ prompt while the program be