088a7eef95
The debugger is always entered after some kind of kernel trap, often a breakpoint in kdb_enter(). This means that the most recent trapframe will include kernel state at the time of the trap, when often it is desirable to the developer to view the contents of the previous trapframe. This trapframe often corresponds to the entry from userspace. The ddb(4) man page claims the ability to display user register state via the 'u' modifier to `show registers`, but this appears untrue. It is not obvious from a quick search of the history when this feature was added, or when it was removed. (Re)implement this feature in db_show_regs, noting that it is not necessarily populated with userspace state. Reviewed by: jhb (earlier version), markj, bcr (manpages) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D27705 |
||
|---|---|---|
| .. | ||
| db_access.c | ||
| db_access.h | ||
| db_break.c | ||
| db_break.h | ||
| db_capture.c | ||
| db_command.c | ||
| db_command.h | ||
| db_examine.c | ||
| db_expr.c | ||
| db_input.c | ||
| db_lex.c | ||
| db_lex.h | ||
| db_main.c | ||
| db_output.c | ||
| db_output.h | ||
| db_print.c | ||
| db_ps.c | ||
| db_run.c | ||
| db_script.c | ||
| db_sym.c | ||
| db_sym.h | ||
| db_textdump.c | ||
| db_thread.c | ||
| db_variables.c | ||
| db_variables.h | ||
| db_watch.c | ||
| db_watch.h | ||
| db_write_cmd.c | ||
| ddb.h | ||