This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug sim/10362] lm32 simulator does not handle non-zero load address
- From: "vapier at gentoo dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 28 Dec 2015 00:21:40 +0000
- Subject: [Bug sim/10362] lm32 simulator does not handle non-zero load address
- Auto-submitted: auto-generated
- References: <bug-10362-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10362
Mike Frysinger <vapier at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Mike Frysinger <vapier at gentoo dot org> ---
it's not clear to me what your expectations are. the memory-region command
does *not* change where code is loaded ... instead, it just connects a chunk of
memory to the addr that you requested. so when you use "memory-region
0x40000000,0x4000000", that connects a chunk of memory at address 0x40000000
with a length of 0x4000000 bytes.
the "load" command is used to control where to load the requested file -- since
you didn't specify any arguments, it uses an offset of 0 (the default).
an example run:
$ ./gdb/gdb -q ./sim/testsuite/pass.s.x
(gdb) target sim --memory-region 0x40000000,0x4000000
Connected to the simulator.
(gdb) load
Loading section .text, size 0x24 lma 0x0
Loading section .data, size 0x102a lma 0x1024
Start address 0x0
Transfer rate: 33392 bits in <1 sec.
(gdb) sim memory-info
Memory maps:
memory region 0x40000000,0x4000000
memory region 0x00000000,0x10000
i'm going to close this bug assuming that you're mixing up the behavior of the
memory-region command. please re-open with more details for us to look at (and
attach some example ELFs for us to test with).
--
You are receiving this mail because:
You are on the CC list for the bug.