OK,

Take 3.

Now i believe this is the final patch required.

I have added comments for Changelog, and i believe i have tracked all 
issues i previously listed.

gdb_loc is the same as before, it return the address of entry_point when 
there are no registers as current $pc.  Seems fine, and the most 
appropriate default.

The problem i listed as 1.c) about the pop up showing: (Internal error: 
pc 0x0 in read in psymtab, but not in symtab.).  Was actually through a 
side effect causing error 1.b) the 3 Drop downs present under the button 
bar for file, function and mode failing to appear.  I get rid of the pop 
up warning box, and the 3 drop downs re-appear, strange i know.  My 
presumption is that the error box was preventing a sequence of code 
executing.

All of the other problem were because I had a number of GDB debug flags 
set to 1.  The messages generated by these debug flags being enabled 
confused insight and produced the rest of my reported problems.

That was certainly "a trap for young players".  And took me most of the 
night to identify.  Its far from intuitive that debug flags will cause 
bugs in their own right.

Word of warning to everyone. GDB debug flags are incompatible with 
insight.  If you need to use them, use --nw find your problem, fix it, 
and disable the debug flags "before" worrying about insight.  Otherwise 
you will get all sorts of strange results. And you might end up pulling 
your hair out for days before identifying what i just did as the cause.

So no patch required to fix 2.b-2.g of my second report, as they are all 
caused by GDB debug message options being enabled.

Comments or Criticisms?

Steven Johnson