Re: cygwin runtime woes

[Keith Seitz <keiths@redhat.com>]

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