Raúl Sánchez Siles schrieb:
With the help of a guy at #gdb I noticed that
msp430 simulator was not enabled in the gdb/configure.tgt file. I've
refreshed [2] so that it should work now.
yep, simulator is selectable again. thanks.
there are two other problems.
1)
and the call stack isn't showing a stack. it shows the correct function
and depth, but repeats the same name on every level instead of keeping
the correct name of the calling function.
2)
running an app, it sometimes ask:
"make a breakpoint on future shared library load?"
--> Yes --> Segmentation fault
--> No --> debugging works
i'm probably doing something wrong i can't get a usable stack trace to
locate the problematic code...
$ gdb --core ./core /opt/mspgcc/bin/msp430-insight
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
Cannot access memory at address 0x7fd92d3b9c88
(gdb) bt
#0 0x00000000005139cb in gdb_get_breakpoint_info
(clientData=0x7fff353aed30, interp=0xab43a0, objc=0, objv=0x0) at
.././gdb/gdbtk/generic/gdbtk-bp.c:314
Cannot access memory at address 0x7fff353aed78
(gdb)
chris
