ad 6e89a762d6 Default DDB_ONPANIC to zero. The end product is ultimately for the ...

consumption of users external to the project, users who are unlikely to
be kernel hackers with the motivation to debug crashes. In this situation
rebooting and creating a crash dump is more appropriate than interrupting
normal service for an unbounded amount of time, while also leaving the
machine at cryptic db> prompt.

2009-01-30 21:30:56 +00:00

..

db_access.c

…

db_access.h

…

db_aout.c

…

db_aout.h

…

db_break.c

…

db_break.h

…

db_command.c

Fix my bug introduced in rev 1.98 of db_command.c where command prefix

2009-01-05 22:19:40 +00:00

db_command.h

Fix my bug introduced in rev 1.98 of db_command.c where command prefix

2009-01-05 22:19:40 +00:00

db_elf.c

…

db_examine.c

more <sys/buf.h> police

2008-11-16 19:34:29 +00:00

db_expr.c

…

db_extern.h

…

db_input.c

…

db_interface.h

Add some basic DDB stuff for modules.

2008-11-25 15:14:07 +00:00

db_lex.c

…

db_lex.h

…

db_output.c

…

db_output.h

…

db_print.c

…

db_run.c

…

db_run.h

…

db_sym.c

As discussed on tech-kern: mutex_init is too heavyweight for early bootstrap

2008-11-30 18:21:31 +00:00

db_sym.h

…

db_trap.c

…

db_variables.c

Default DDB_ONPANIC to zero. The end product is ultimately for the

2009-01-30 21:30:56 +00:00

db_variables.h

…

db_watch.c

…

db_watch.h

…

db_write_cmd.c

…

db_xxx.c

Add some basic DDB stuff for modules.

2008-11-25 15:14:07 +00:00

ddbvar.h

…

files.ddb

…

TODO

…