GDB

Gnu debugger (6.3 and 6.5) for cygwin (called cygwin-special in version-postfix) seems to have a burried feature. How can it manage that Eclipse stops a running process? A standard compiled gdb is not able to do so. cygwin-special gdb uses some DLLs not implicitly clear to know why (i.e. COMCTR

Signalling of non console application

How can applications be signalled (i.e. CTRL+C) if they have no console? My problem is sourced in a GDB cross debugger that does not stop if it is Eclipse controlled, but it stops without problems in a console. On the other hand the cygwin-special gdb (built by redhat/cygwin as I suppose, not by