[gvd-devel] GVD Memory Window

[Tom Bridgwater]

Hi,

I was just trying out the Win32 binary of GVD 1.2.5 (20020125) and =
noticed that the memory window doesn't seem to work...

When I enter a location it just hangs, but then I press enter at the gdb =
prompt and I see the output of what seems to be a 'x/4096bx' command on =
an address about 1K (0x0408) after what I wanted to see in the memory =
window. The memory window just remains blank. When this happens, the =
mouse cursor changes to a watch when I move it over the status bar.

If I open the memory window and enter a location before connecting to =
the target, it fills the window with '--'. After that I can connect and =
then click 'view' in the memory window again and it hangs as I =
described, but this time after I press enter at the GDB prompt and I see =
the output of the 'x' command - the memory window shows me the data from =
the output of the 'x' command (which is ~1K higher than the location I =
entered).

I'm starting GVD with the "--debugger" command line parameter to start =
gdb (v5.1, host=3Di686-pc-cygwin, target=3Darm-elf), and connecting at =
the gdb prompt with "target remote localhost:2001" (only the debugger =
name is filled in on the "new debugger" window).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tom Bridgwater
Software Engineer
650.230.5123
tbridgwater@handspring.com
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handspring Treo
phone, organizer, web, and email all in one
Treo is now shipping!  Visit www.handspring.com