View mode: basic / threaded / horizontal-split · Log in · Help
February 28, 2008
Descent & ddbg: GUI shows no stack trace when program die
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.
February 28, 2008
Re: Descent & ddbg: GUI shows no stack trace when program die
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.
Top | Discussion index | About this forum | D home