Date: Fri, 13 Mar 1998 10:03:28 +0200 (EET)
From: Andris Pavenis <pavenis AT latnet DOT lv>
To: steve <swinter AT mediaone DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: [Q] How to get call stack after assert in RHIDE
In-Reply-To: <350854EB.7906@mediaone.net>
Message-ID: <Pine.GSO.3.96.980313095417.4354B-100000@sisenis>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk



On Thu, 12 Mar 1998, 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?
> 
> Thanks
> Steve:-O
> 

RHIDE currently kills the program if such signal as SIGINT, SIGSEGV, SIGABRT
is encountered so the stack is no more available. I tried to change this
behaviour in Linux version for SIGINT to be able to stop program with Ctrl-C
and continue debugging (I didn't try this for DJGPP as I was not able to get
correct reaction to SIGINT in GDB.EXE I built from sources). 

About redefining assert macro: it should work. 

One more way: Use gdb.exe directly. It is not so complicated as it can
look initially.

Andris