- Goals
- User guide
- History
- Application testing list
- Getting Started
- Hardware Compatibility List
- Hardware requirements
- JNode Commands
- acpi
- alias
- arp
- basename
- beep
- bindkeys
- bootp
- bsh
- bzip2
- cat
- cd
- class
- classpath
- clear
- compile
- console
- cpuid
- date
- del
- device
- df
- dhcp
- dir
- dirname
- disasm
- echo
- edit
- eject
- env
- exit
- gc
- grep
- gzip
- halt
- help
- hexdump
- history
- ifconfig
- java
- kdb
- leed, levi
- loadkeys
- locale
- log4j
- ls
- lsirq
- man
- memory
- mkdir
- mount
- namespace
- netstat
- onheap
- page
- ping
- plugin
- propset
- pwd
- ramdisk
- reboot
- remoteout
- resolver
- route
- rpcinfo
- run
- startawt
- syntax
- tar
- tcpinout
- thread
- time
- touch
- unzip
- utest
- vminfo
- wc
- zip
- JNode GUI
- JNode Shell
- Performance
- Status
- Classlib developers guide
- Developer guide
- Tester guide
- Porting guide
- Blogs
- Project development
- Glossary
- Proposals
- FAQ
- Papers & presentations
- References
- Research
kdb
kdb
| Synopsis | ||
| kdb | show the current kdb state | |
| kdb | --on | turn on kdb |
| kdb | --off | turn off kdb |
|
Details | ||
|
The kdb command allows you to control "kernel debugging" from the command line. At the moment, the kernel debugging functionality is limited to copying the output produced by the light-weight "org.jnode.vm.Unsafe.debug(...)" calls to the serial port. If you are running under VMWare, you can configure it to capture this in a file in the host OS.
The kdb command turns this on and off. Kernel debugging is normally off when JNode boots, but you can alter this with a bootstrap switch. |
||
