> Yes, try the 'catch throw' command in gdb -- that should break on the
> throw itself, and will give a useful stack trace (in my quick
> testing) ;)
Thanks, but that's not exactly what I'm looking for. I only want gdb to break
when the exception is not caught. Using the 'catch throw' command
Christopher Faylor cygwin.com> writes:
> gdb does not just exit with an uncaught exception. It responds to a SIGSEGV
> the same way as linux.
Can cygwin gdb print a stack trace that would direct me to the throw -1 line
when debugging the following program?
int main() {
throw -1;
return 0
Christopher Faylor cygwin.com> writes:
> gdb does not just exit with an uncaught exception. It responds to a SIGSEGV
> the same way as linux.
Hmm, I guess that's good that it's supposed to be doing what I want it to, but I
can't get it to work.
If I debug this example program with gdb:
int ma
On Mon, Sep 18, 2006 at 06:16:51PM +, Ryan Boder wrote:
>In Linux, if I am using gdb on a program and it throws an exception that is not
>caught, I can then get a stack trace with the bt command.
>
>In Cygwin, the program just exists and I see the following line:
>
>Program exited with code 040
4 matches
Mail list logo
