• nobody (11/11) Feb 27 2008 I tried to use Descent & ddbg
• Ary Borenszweig (10/26) Feb 28 2008 Currently the debugger interface doesn't handle unhandled exception. I

nobody <some where.com> writes:

I tried to use Descent & ddbg

When the program dies because of a null pointer, there's no stack trace shown
in the Debug tab.

The Console tab shows:
...
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION(0xc0000005) at ...

and the Debug tab still shows running
...
-- Thread [main] (Running)


I then tried ddbg alone from its command line interface, it actually has all
the info. So I think Descent should show them.

Ary Borenszweig <ary esperanto.org.ar> writes:

nobody escribió:
 I tried to use Descent & ddbg
 
 When the program dies because of a null pointer, there's no stack trace shown
 in the Debug tab.
 
 The Console tab shows:
 ...
 Unhandled Exception: EXCEPTION_ACCESS_VIOLATION(0xc0000005) at ...
 
 and the Debug tab still shows running
 ...
 -- Thread [main] (Running)
 
 
 I then tried ddbg alone from its command line interface, it actually has all
 the info. So I think Descent should show them.

Currently the debugger interface doesn't handle unhandled exception. I 
guess it should behave as if someone put a breakpoint there, right? 
Stopping the execution of the program, showing the stack trace, allowing 
you to see the variables, etc.

I added an enhancement request for this: 
http://www.dsource.org/projects/descent/ticket/62

However, you can still talk to ddbg in Descent in the Console view. Go 
there and type "us", for example, or any other command... at least until 
I implement the enhancement.