This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
SIGTRAP question
- To: ecos-discuss at sourceware dot cygnus dot com
- Subject: [ECOS] SIGTRAP question
- From: Nicole Cook <cook at maya dot com>
- Date: Thu, 11 May 2000 15:15:33 -0400
I keep running into this problem while debugging with ecos gdb stubs - I
can't seem to figure out where the SIGTRAP is coming from. I'm running
arm-elf-gdb on linux, debugging an aebC. I can't figure out where the
sigtrap is coming from - it just never returns from the function? Is
there something set in the stubs to trigger this trap?
(gdb) load
Loading section .rom_vectors, size 0x60 lma 0xc000
Loading section .text, size 0x122a0 lma 0xc060
Loading section .rodata, size 0x930 lma 0x1e300
Loading section .data, size 0x314 lma 0x1ec30
Start address 0xc060 , load size 77636
Transfer rate: 27003 bits/sec, 304 bytes/write.
(gdb) c
Continuing.
Mapping peripheral into address space...
Reading drive info; Vinton's code relies on side-effects...
...done
Last block address 6354431
Cylinder 6303, head 15, sector 63
Breakpoint 2, IDE_onPowerUp () at lba.c:611
(gdb) s
(gdb) s
Program received signal SIGTRAP, Trace/breakpoint trap.
0x401a5e4 in ?? ()
(gdb) s
Cannot find bounds of current function
(gdb)