Well, if I simply execute GDB, connect to the target and load the
symbol file afterwards then it seems to work. Strange behaviour....
Nevertheless, debugging still doesn't seem to work properly. (see
snipplet below)
---snip---
m68k-bdm-gdb
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-bdm-elf".
(gdb) target remote board:3000
Remote debugging using board:3000
0x03c70048 in ?? ()
(gdb) add-symbol-file uClinux-dist/user/ping/ping.gdb 0x03c70048
add symbol table from file "uClinux-dist/user/ping/ping.gdb" at
.text_addr = 0x3c70048
(y or n) y
Reading symbols from
/projekte/DZA4/23_SW_Erstellung/uClinux-dist/user/ping/ping.gdb...done.
(gdb) break main
Breakpoint 1 at 0x3c70636: file ping.c, line 212.
(gdb) c
Continuing.
Breakpoint 1, main (argc=64405360, argv=0x1) at ping.c:212
212 {
(gdb)
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x03c7063e in main (argc=2, argv=0x3ccbf78) at ping.c:212
212 {
---snap---
Zitat von Markus Franke <[EMAIL PROTECTED]>:
Hi Kieran,
Zitat von Kieran Bingham <[EMAIL PROTECTED]>:
reading those now ... looks like you were getting identical to me ...
gdb assumes everything loads from 0x0
I've got round that by using the add-symbol-file
well, this doesn't help in my case. Besides, I provide the symbol file
already on startup of gdb for example by calling:
---snip---
m68k-bdm-gdb uClinux-dist/user/ping/ping.gdb
---snap---
But even after explicitly loading the symbol file again as you
proposed I get:
---snip---
m68k-bdm-gdb uClinux-dist/user/ping/ping.gdb
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=m68k-bdm-elf"...
(gdb) target remote board:3000
Remote debugging using board:3000
0x03cf0048 in ?? ()
(gdb) add-symbol-file uClinux-dist/user/ping/ping.gdb 0x03cf0048
add symbol table from file "uClinux-dist/user/ping/ping.gdb" at
.text_addr = 0x3cf0048
(y or n) y
Reading symbols from
/projekte/DZA4/23_SW_Erstellung/uClinux-dist/user/ping/ping.gdb...done.
(gdb) b main
Cannot access memory at address 0x5ee
---snap---
I have the feeling that there might be something wrong with my *.gdb
symbol files?!?!?
Thanks for the hint anyway and good luck for your breakpoint problem. ;-)
With best regards,
Markus
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
