To Vladimir Prus: Debugger in 3.4.0

[Vladimir Prus]

On Monday 05 March 2007 12:37, Leon Pollak wrote:
> Just in the case Vladimir missed this, I resend my last mail.
> Vladimir, please, can you look at this (I have no access to your 
> ghost at cs.msu.su mail)?
> 
> On Wednesday 28 February 2007, Vladimir Prus wrote:
> > Leon,
> > I'm afraid that due to large email volume here,  I forgot what
> > are "the problems" you refer to, so cannot tell if they
> > are likely to be caused by gdb 6.5. I generally suggest 6.6, but 6.5 should
> > be usable too.
> Thanks, Vladimir.
> 
> The most heavy problem I have is that each time I press "step" button or 
> debugger stops at BP I receive the error message "Debugger reported the 
> following error: Previous frame inner to this frame (corrupt stack?) ". Below 
> is the debugger window output in "Show all" mode:

This, for all appearences, seems to be a gdb problem. Gdb cannot produce 
backtrace for your architecture/OS -- either that's wrong gdb, or something
is buggy in it.

> <font color="blue">(gdb) -stack-info-depth 6</font>
> Previous frame inner to this frame (corrupt stack?)
> ^error,msg="Previous frame inner to this frame (corrupt stack?)"
> <font color="blue">(gdb) -var-update *</font>

This is just basic backtrace command.

> ^done,changelist=[]
> 
> ---------------------------------------------------------------------------
> 
> Plane gdb and DDD do not issue any error messages and work fine.

Did you try "backtrace" in plain gdb?

- Volodya