Re: showing the gdb commands executed by insight ?

[Jim Sullivan <jamessul at cisco dot com>]

Hi Keith, 

Here is an overview of my environment and the problem I am trying
to solve. 

I am using a remote target. 
For debugging I typically 
1. startup insight with the symbol file in the same directory. 
2. set the target setting to remote serial, or remote tcp ...etc.   
3. connect to the target 
 
All this works great. 
I can also disassem code after step 1 above, which implies
that I do not have to be connected to the target to read 
the code. I would guess that insight looks at the symbol  
file, and object file to dump this information. 

Now if I wanted to do the same thing using GDB. 
I.e. disassem the code without connecting to the target
I would think that I need only provide a symbol file
and the location of the source, however your previous
response implies it is more involved that this. 

more comments below.  


On Fri, 2005-01-14 at 12:11, Keith Seitz wrote:
> On Fri, 2005-01-14 at 08:39, Jim Sullivan wrote:
> > If I run insight and give it a symbol file 
> > I can disassemble the code and it works correctly. 
> 
> Sometimes.

Can you explain ? 

> If you're using a remote target, I'll bet it appears to work because
> insight always disassembles from the image file (as I recall). Gdb, on
> the other hand, will disassemble from memory, so if you haven't loaded
> an image onto your target, you're going to get gibberish.

This would seem to explain it, but using 
set trust-readonly-sections did not solve the problem. 

thanks, Jim