This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
gdb internal error
- From: ananda dot motte at philips dot com
- To: gdb at sources dot redhat dot com
- Date: Thu, 22 Nov 2001 18:19:12 +0100
- Subject: gdb internal error
Hello all
I am using arm-elf-gdb with the simulator as target.
I wrote a linker script to map certain sections to regions of memory defined in my linker script
MEMORY{
FLASH_ROM (rx) : org = 0x08000000, len = 0x60000
SRAM_BANK0 (r): org = 0x20000000, len = 0x4000
SRAM_BANK1 (r): org = 0x20004000, len = 0x4000
SRAM_BANK2 (rx): org = 0x20008000, len = 0x4000
SRAM_BANK3 (r): org = 0x2000C000, len = 0x4000
DRAM (rwx): org = 0xC0700000, len = 0x100000
MMU (!i): org = 0x08058000, len = 0x4000
}
SECTIONS{
. = 0x08000000;
.FLASHROM : {
Startup.o(.StartupArea)
} > FLASH_ROM
_eStartupArea = ABSOLUTE(.) ;
.SRAMBANK0 0x20000000 : AT(ADDR(.FLASHROM)+SIZEOF(.FLASHROM)){
Startup.o(.SramBank0Base)
} > SRAM_BANK0
_eSramBank0Base = ABSOLUTE(.);
.SRAMBANK1 0x20004000 : AT(_eSramBank0Base){
Startup.o(.SramBank1Base)
} > SRAM_BANK1
_eSramBank1Base = .;
.SRAMBANK2 0x20004000 : AT(_eSramBank1Base){
Startup.o(.SramBank2Base)
} > SRAM_BANK2
_eSramBank2Base = .;
.SRAMBANK3 0x20004000 : AT(_eSramBank2Base){
Startup.o(.SramBank3Base)
} > SRAM_BANK3
_eSramBank3Base = .;
.DRAM : AT(_eSramBank3Base){
_sloadtextSwap = .;
*(.rodata)
*(.text)
*(.textSwap)
*(.textSort)
*(.data)
*(.ctors)
*(.dtors)
*(.eh_frame)
__bss_start__ = .;
*(.bss)
*(.sbss)
__bss_end__ = .;
*(.sdata)
_eloadtextSwap = .;
_eDRAM = .;
_lentextSwap = _eloadtextSwap - _sloadtextSwap;
}
_simagetextSwap = 0xC0700000;
.MMU : AT(_eDRAM){
MMU.o(.comm)
} >MMU
}
end = 0x08058000 + 0x4000 ;
The link step goes fine and the mapfile is OK. But when I launch Insight configured for arm-elf ( insight+dejagnu-5.0.91_20011023) I get inexplicably
" An internal error GDB error was detected.This may make further debugging unreliable............." and the ilk
When I remove the linker script ha no problem...............
Does this have to do with the address org=.0x08000000 by any chance which is not accessible on my host system ???
Can someone help me to point out why exactly this error occurs and the workaround ( writing a memory map or something )????