Mail Archives: djgpp/1998/03/13/20:22:45
At 09:30 3/12/1998 GMT, steve wrote:
>When debugging in RHIDE and an assert occurs the call stack is always
>shown empty (it would be nice to see the function call stack showing
>how the program got there. When debugging and an error occurs, i.e. GPF,
>the call stack has the function calls as would be expected.
>
>Is there a way to view the call stack in RHIDE after the program aborts
>due to an assert? Maybe a RHIDE option, or a redefinition of the assert
>macro to allow this?
You could set a breakpoint on the function `__dj_assert', which is called
when an assertion fails. Or, as you thought, you can certainly redefine
`assert' for your own purposes.
Nate Eldredge
eldredge AT ap DOT net
- Raw text -