This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
RE: cygwin runtime woes
The -nx made a bigger difference!!!
I had a starting insight !
Thus I removed the gdbtk.ini file
and retried to start insight with gdb.exe
but I got no source window, and when I tried to
load gdb.exe manually after, I got this:
can't set "gdb_loaded": {hook=namespace inscope ::SrcWin {::.srcwin0.srcwin
_set_state} args="gdb_loaded" can't read "twin": no such variable
}
while executing
"set gdb_loaded 0"
(procedure "set_exe" line 24)
invoked from within
"set_exe"
(procedure "_open_file" line 63)
invoked from within
"_open_file"
(menu invoke)errorCode is NONE
> -----Message d'origine-----
> De?: insight-owner@sourceware.org [mailto:insight-owner@sourceware.org]
> De la part de Keith Seitz
> Envoyé?: Wednesday, May 06, 2009 6:11 PM
> À?: Pierre Muller
> Cc?: insight@sourceware.org
> Objet?: Re: cygwin runtime woes
>
> Pierre Muller wrote:
> > I debugged the problem a bit:
> >
> > gdb_loc is call a few times
> > for 'main' 'MAIN___' 'MAIN__' 'cyg_user_start' 'cyg_start'
> > and then finally with '*' which causes the abort.
>
> That sounds normal. When insight starts up and gdb loads an executable,
> it will attempt to locate the entry point for the executable so that
> the
> source window can display it. These function names are actually from
> the
> preference gdb/main_names, defined in prefs.tcl.
>
> The '*' argument is odd. I don't know where that is coming from.
> Passing
> '*' to gdb_loc will cause gdb_loc to error, though.
>
> Out of curiosity, have you tried inhibiting preferences at startup?
> (insight -nx) Does it make any difference?
>
> > the first calls all fail with
> > "No symbol table loaded. Use "file" command"
> > even though I used ./gdb.exe as arg for run command.
>
> That sounds odd, too. Can you start vanilla gdb this way? I wonder what
> insight might be complaining about. Have you tried running insight in
> debug mode? To enable this, set GDBTK_DEBUG=1 in your environment
> before
> starting insight. It will write out the file "insight.log" (which you
> can change by setting GDBTK_DEBUGFILE).
>
> Keith