Abatron for Userland Debugging?
[email protected] wrote on 12/4/01 5:27 pm:
Quoted 6 lines
Why?
You only need Abatron in the
cases where kernel crashes.
There is gdb for user
applications.
Why? Because gdbserver is acting strange (can stop at a breakpoint, but won't step or continue). Maybe it is ptrace acting up, so I thought maybe the Abatron could help...
-kb, the Kent who is thinking the Abatron will be useful in watching ptrace and gdbserver chat with one another.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 2 lines · [email protected] wrote:
-kb, the Kent who is thinking the Abatron will be useful in watching ptrace and gdbserver chat with one another.
You have to be a little bit careful with this.
First, there is a configuration option to add BDI context switch. This switches the user page tables for teh BDI so you can at least look into the process space for the current thread. This is useful for things like system call tracing to see what the application actually did. This is a configuration option because it adds a couple of instruction to the context switch path.
Second, when debugging ptrace or gdb activity with the Abatron, you have to be careful on some processors. For example, on 4xx processors the BDI2000 uses the same processor debug registers as gdb or ptrace would, so you end up fighting over the debug register contents and no one knows what it going on.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/