| Summary: | 5.3-BETA7 kernel config option ALT_BREAK_TO_DEBUGGER doesn't work | ||
|---|---|---|---|
| Product: | Base System | Reporter: | John Engelhart <johne> |
| Component: | kern | Assignee: | Gavin Atkinson <gavin> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.3-BETA7 | ||
| Hardware: | Any | ||
| OS: | Any | ||
On Wed, Oct 13, 2004 at 01:06:55PM +0000, John Engelhart wrote: > options KDB, KDB_UNATTENDED, KDB_TRACE > options ALT_BREAK_TO_DEBUGGER # Use <CR>~^b to enter debugger on > # the serial port > options PANIC_REBOOT_WAIT_TIME=300 > > It looks like the kernel debugger parts changed from 5.2.1 to 5.3, > though, and this may just be that I didn't follow all the details of > what's changed. Previously, instead of KDB, my 5.2.1 config had DDB > and all worked well. KDB is just the kernel debugging framework, it doesn't actually include a debugger. You're missing DDB or GDB. From NOTES: # # Compile with kernel debugger related code. # options KDB # # Enable the ddb debugger backend. # options DDB Kris State Changed From-To: open->analyzed So looks like the documentation is OK and we can just close this PR? State Changed From-To: analyzed->closed Close, feedback timeout (2 years), looks like it was a local config problem. (spotted by vwe) Responsible Changed From-To: freebsd-bugs->gavin Track |
The kernel config option ALT_BREAK_TO_DEBUGGER doesn't seem to work on 5.3-BETA7. From my kernel config: options KDB, KDB_UNATTENDED, KDB_TRACE options ALT_BREAK_TO_DEBUGGER # Use <CR>~^b to enter debugger on # the serial port options PANIC_REBOOT_WAIT_TIME=300 It looks like the kernel debugger parts changed from 5.2.1 to 5.3, though, and this may just be that I didn't follow all the details of what's changed. Previously, instead of KDB, my 5.2.1 config had DDB and all worked well. I've been having ethernet hangs and the debugger didn't seem to want to come up when I'd have the problem. So, after the last round, I tried it when the system had rebooted and was running fine. Didn't drop to debugger then, either. Perhaps I missed something in the 5.2.1 to 5.3 debugger transition. If so, can you post the simple/obvious fix to the kernel conf in case anyone else trips up on this like I did?