This is the mail archive of the
mailing list for the GDB project.
Unable to debug after changing address of the '.stack' section
- From: "Ina Pandit" <Ina dot Pandit at kpitcummins dot com>
- To: <gdb at sourceware dot org>
- Cc: "Ina Pandit" <Ina dot Pandit at kpitcummins dot com>
- Date: Tue, 7 Apr 2009 20:48:21 +0530
- Subject: Unable to debug after changing address of the '.stack' section
- References: <82C3BC9106BCE149B63464D79D0A22FD0A1F6FA3@sohm.kpit.com> <82C3BC9106BCE149B63464D79D0A22FD0A1F746B@sohm.kpit.com>
I created a simple 'Hello World' application and built it using gnu
toolchain for SH target.
sh-elf-gcc foo.c -g
I could successfully debug the application using SH gdb
simulator (target sim) with the default linker script provided
by the toolchain.
However, if I change the address of the '.stack' section
(using a custom linker script) from '0x300000' (default)
to '0xFFFF0000', the following error message is displayed
while running (r) the application,
Program received signal SIGEMT, Emulation trap.
0x000011a8 in atexit ()
Also, if the address of the '.stack' section is changed to
'0x00FF0000', the applications runs successfully.
Is there a limitation on the address range that can be specified
(in the linker script), while debugging using gdb simulator?
Are there some additional settings or steps required for
accessing this memory area (while debugging)?
Any help on this topic will be highly appreciated.
Thanks in advance.