Date: Fri, 13 Mar 1998 17:21:49 -0800 (PST)
Message-Id: <199803140121.RAA05954@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: steve <swinter AT mediaone DOT net>, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: [Q] How to get call stack after assert in RHIDE
Precedence: bulk

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