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. COMCTRL.DLL, Tickle DLLs). Are they used therefore? Is it a redhat secret how it works (non-open-source)? If possible, please let me know how to manage that the signal(..) function can be used for CTRL+C on standard streams owned by a windows application as Eclipse. With best regards Philipp Schraner
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
