FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2014-04-07T02:36:30Z 2014-04-07T02:36:30Z Pedro F. Giffuni pfg@FreeBSD.org 2014-04-07T02:36:30Z urn:sha1:7ad20d8f434eac0c72ff4d6243340fc5da6c2d21 ddb: Minor style cleanups. #define should be followed by tab. 2012-05-21T21:14:09Z John Baldwin jhb@FreeBSD.org 2012-05-21T21:14:09Z urn:sha1:3dea1ae476e0aeb90feb69643e4feb8957b1ff08 - Extend the KDB interface to add a per-debugger callback to print a backtrace for an arbitrary thread (rather than the calling thread). A kdb_backtrace_thread() wrapper function uses the configured debugger if possible, otherwise it falls back to using stack(9) if that is available. - Replace a direct call to db_trace_thread() in propagate_priority() with a call to kdb_backtrace_thread() instead. 2012-05-14T13:49:06Z Sergey Kandaurov pluknet@FreeBSD.org 2012-05-14T13:49:06Z urn:sha1:e7228dd33c2f74f4a1915b7f13310657b88636c5 Use FOREACH_PROC_IN_SYSTEM instead of using its unrolled form. 2012-01-02T00:01:09Z Konstantin Belousov kib@FreeBSD.org 2012-01-02T00:01:09Z urn:sha1:8529163c3d9cfc46e89d8f6f2b921778124c6f8d Add 'findstack' ddb command to search either the thread kernel stack or cached stack containing the specified kernel virtual address. 2012-01-01T23:58:20Z Konstantin Belousov kib@FreeBSD.org 2012-01-01T23:58:20Z urn:sha1:f24504ce9aea9a0f11728f526c496b7435f20632 2011-12-30T20:06:43Z Konstantin Belousov kib@FreeBSD.org 2011-12-30T20:06:43Z urn:sha1:14eefa27cfafc97be83436b498d2fcf52dafb6f1 Typo. 2011-08-27T14:24:27Z Robert Watson rwatson@FreeBSD.org 2011-08-27T14:24:27Z urn:sha1:e5a0927394502ac7d7d0383c523490eb35f773dc improvements: (1) Implement new model in previously missed at91 UART driver (2) Move BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER from opt_comconsole.h to opt_kdb.h (spotted by np) (3) Garbage collect now-unused opt_comconsole.h MFC after: 3 weeks Approved by: re (bz) 2011-06-07T01:28:12Z Marcel Moolenaar marcel@FreeBSD.org 2011-06-07T01:28:12Z urn:sha1:299cceef036de62905e745118b4710b73b48d3c3 for it. Do not not expect a developer to call doadump(). Calling doadump does not necessarily work when it's declared static. Nor does it necessarily do what was intended in the context of text dumps. The dump command always creates a core dump. Move printing of error messages from doadump to the dump command, now that we don't have to worry about being called from DDB. 2011-04-28T17:59:33Z John Baldwin jhb@FreeBSD.org 2011-04-28T17:59:33Z urn:sha1:41b1c2596025ea68dcaf411731fcddafa4e89c27 MFC after: 1 week 2011-04-27T16:43:03Z Attilio Rao attilio@FreeBSD.org 2011-04-27T16:43:03Z urn:sha1:7126ba42f6aed181e974246d46bfe3409da8b8ac the watchdog, via the watchdog(9) interface. For that, the WD_LASTVAL bitwise operation is used. It is mutually exclusive with any explicit timout passing to the watchdogs. The last timeout can be returned via the wdog_kern_last_timeout() KPI. - Add the possibility to pat the watchdogs installed via the watchdog(9) interface from the kernel. In order to do that the new KPI wdog_kern_pat() is offered and it does accept normalized nanoseconds or WD_LASTVAL. - Avoid to pass WD_ACTIVE down in the watchdog handlers. All the control bit processing should over to the upper layer functions and not passed down to the handlers at all. These changes are intended to be used in order to fix up the watchdog tripping in situation when the userland is busted, but protection is still wanted (examples: shutdown syncing / disk dumping). Sponsored by: Sandvine Incorporated Reviewed by: emaste, des, cognet MFC after: 2 weeks