From: jmerkey@wolfmountaingroup.com
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.27-rc1 24/25] mdb: Merkey's Kernel Debugger 2.6.27-rc1
Date: Mon, 4 Aug 2008 00:42:37 -0600 (MDT) [thread overview]
Message-ID: <45485.166.70.238.45.1217832157.squirrel@webmail.wolfmountaingroup.com> (raw)
Netware style debugger for Linux written by Jeffrey Vernon Merkey
--- a/lib/Kconfig.debug 2008-08-03 16:10:19.000000000 -0600
+++ b/lib/Kconfig.debug 2008-08-03 16:15:00.000000000 -0600
@@ -134,6 +134,31 @@
Say Y here if you are developing drivers or trying to debug and
identify kernel problems.
+config MDB
+ bool "Merkey's Kernel Debugger"
+ depends on DEBUG_KERNEL
+ select KALLSYMS
+ select KALLSYMS_ALL
+ help
+ NetWare style kernel debugger for Linux written by Jeffrey Vernon
+ Merkey.
+
+config MDB_CONSOLE_REDIRECTION
+ bool "MDB Console Redirection Support"
+ depends on MDB
+ default y
+ help
+ Reset any Console Redirection to default system settings (0)
+ when the MDB debugger is active. The Debugger will restore
+ the redirection to the custom settings when the debugger
+ is exited. This feature is useful on systems which by default
+ redirect printk output and the screen debugger output to a log
+ file or system device, which can prevent the debugger screen from
+ being visible. Enabling this feature does not affect or disable
+ remote operations via serial port. It is recommended to enable
+ this feature by default if intensive debugging is intended for
+ the target system.
+
config DEBUG_SHIRQ
bool "Debug shared IRQ handlers"
depends on DEBUG_KERNEL && GENERIC_HARDIRQS
By making a contribution to this project, I certify that
the contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file.
Jeffrey Vernon Merkey
reply other threads:[~2008-08-04 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45485.166.70.238.45.1217832157.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®