I tried it with 2 different executables (both C++, both compiled with GCC3.2). I tried it with both the stock gdb (20010428-3) & the one listed as experimental (20020718-1). I also tried it with both 1.3.13-2 & 1.3.12-4.
The test was, set a breakpoint at the first line of main (done by default by the gui), and click the run button. With both programs & both versions of GDB, the results were the same: With 1.3.12-4, it worked fine. With 1.3.13-2, gdb got the sigsegv signal. I don't know if this is a problem with gdb, or with cygwin (maybe the new malloc?). -Rolf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/