Re: Memory window problems

[Keith Seitz <keiths@redhat.com>]

Wilfried Fauvel wrote:

>> What version are you using ("show version" in console or "insight -v"
>> from command line)?
>>
> 
> $ ./sparc-tsim-elf-insight.exe -v
> GNU gdb 6.4.0.20051202-cvs
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "--host=i686-pc-cygwin --target=sparc-tsim-elf".

Ah, so you aren't really using a cygwin version. You're using a 
cygwin-hosted sparc-tsim-elf version.

Can you inspect the memory in gdb? Is it valid or the same as insight? I 
recommend doing this from command-line gdb (sparc-tsim-elf-gdb.exe) 
using the "x" command (see "help x"). That way if it is still wrong, you 
can take a capture of the whole session and send it to the gdb list or 
file a bug against gdb. :-)

I really doubt that it is insight causing the problem. Insight has very 
little target-specific code. [Remember: insight is the GUI (and tons of 
"glue code) for gdb. Gdb still does all the "work".]

There is at least one question (rhetorical) that I ask myself about this 
since you are using a non-native target. Alas, I have not used or 
thought about embedded/non-native debugging for so long, that I don't 
know the answer(s) anymore.

Nonetheless, let's see what GDB thinks is at that memory. If it is 
right, I will probably need a testcase (a simple exe so that I don't 
have to build the compiler) to reproduce here.

Keith