Re: _status: no such variable

Re: _status: no such variable

[Phil Edwards]

[Insight list added to cc line.]


On Tue, Jan 09, 2001 at 06:24:03AM -0500, Fernando Nasser wrote:
> 
> Furthermore, this stack trace describes an impossible situation. 
> "_status" is
> where the Source Window stores the name of the label widget that is used
> for status and help information (at the bottom).  Regardless of the success
> or not of the creation of this widget the variable should exist. "no such
> variable" is just absurd.

Well, I don't know what to tell you...

Should I send a screenshot of the window containing the message?

Would you like to come over and look at it?  Let's see... you're in Toronto,
I'm in Ohio... if you can make it here by lunchtime I can leave it on the
screen until then.  :-)


> There are two possibilities remaining:
> 
> 1) Your cvs checkout went terribly wrong.  A fresh checkout should fix
> it.

Nope, CVS was fine.


> 2) You are loading some program (you called GDB with an executable name
> in
>    the command line).  Something went wrong with the symbol reading and
> GDB
>    did a longjump in some uncaught situation (I thought we got rid of
> those
>    though).  Please try opening GDB without specifying a file.

Okay.  *tries*  Well, the windows appear.  But the Source Window is
completely blank; no menubar.

Fortunately, I have the Console Window already popped by default.  I tried
loading the executable then, but:

    (gdb) load a.out
    Error: You can't do that when your target is `None'

    (gdb) 

Any thoughts?


Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

Re: _status: no such variable

[Tom Tromey]

Phil> Okay.  *tries* Well, the windows appear.  But the Source Window
Phil> is completely blank; no menubar.

I think the error you are seeing is a side effect of this.
For instance if SrcWin::_build_win fails in some way that leaves
_status unset, then you could see this bug.

This means you have to work backwards to find the earlier error.
One way might be to set GDBTK_DEBUGFILE (to a file name or `stderr')
and then run insight.  Then look in the log to see if there is another
error message.

Tom