From: "jidong xiao" <jidong.xiao@gmail.com>
To: jmerkey@wolfmountaingroup.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger
Date: Mon, 11 Aug 2008 18:36:35 +0800 [thread overview]
Message-ID: <4104961b0808110336x74676e9ane135d2e8c11ccea@mail.gmail.com> (raw)
In-Reply-To: <17494.166.70.238.46.1217784156.squirrel@webmail.wolfmountaingroup.com>
On Mon, Aug 4, 2008 at 1:22 AM, <jmerkey@wolfmountaingroup.com> wrote:
>
>
> This is a linux port of the kernel debugger I wrote in 2000 for the
> MANOS/Gadugi Operating System. I created this particular
> port in June of this year from the MANOS/Gadugi source code I released
> under the GNU public license in 2000.
>
> I wrote the SMP debugger use in SMP Netware in 1994 and 1995, and that was
> later rolled into the main Netware kernel, though a lot of folks
> contributed helped merge it into Netware. This debugger closely resembles
> the legacy Netware kernel debugger, and I find it easier to use than kdb
> with less
> crashes and problems.
>
> This version is ia32 only at present, but I am completing x86_64 support
> and will post it as it is completed. I basically wrote this tool for
> my own internal use and for my projects since I could not find a debugger
> in linux I was used to. I add support to it as I need it for my own
> internal use.
>
> This linux port of my kernel debugger does not require kdb or the kdb hooks
> and is more minimal than kdb and has some features kdb does not, such as
> Intel style disassembly with dereferencing of data during disassembly
> and a very robust mathematical numeric support with conditional breakpoints.
>
> I created a far more robust version of this debugger in 2001 which
> included source level support, integrated screen and keyboard support,
> remote networking capability, and loader support and licensed it to another
> company. I was placed under a 5 year non-compete not to port
> this tool to Linux until end of year 2007. The folks who licensed it
> did absolutely nothing with it of consequence, and 2007 has come and gone,
> so I am released from the non-compete and decided to port the debugger
> from my old Open Source operating system and I figured it might be as useful
> to others as it has been for my projects.
>
> I will be posting user space modules which can be loaded with this version
> at some point which will enable source level debugging and a bunch of
> other features. This add ons may get farmed out to another company for
> support.
>
> KNOWN ISSUES
> ------------
>
> This debugger works very well on SMP systems, but some of the directed
> NMI features are intended for post mortem crashed systems.
>
> All numbers entered are interpreted as hex. If you want a number
> interpreted from the debugger console in decimal, add an 'r' to the end of
> the number for "real number".
>
> There is awesome help support in the debugger. type "help" or "help
> <command name>".
>
> I have support for post-mortem directed NMI breakpoints from the debugger
> console if you want to halt another processor which can hang on some
> systems, but usually does not.
>
> I do not have ia64 support and since Intel in 2000 refused to share ia64
> information with me, I never completed the ia64 section of the debugger.
> If and when I obtain an ia64 system, I will look into putting it in or
> try to adapt the disassembler out of kdb which has ia64 and x86_64 support.
>
>
>
> vanilla kernels
>
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.18-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.19-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.20-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.21-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.22-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.23-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.24-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.25-ia32-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.26-ia32-08-02-08.patch
>
>
> Linux distributions
>
> ftp://ftp.wolfmountaingroup.org/pub/mdb/distro/mdb-2.6.16-ia32-SLES-10-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/distro/mdb-2.6.18-el5-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/distro/mdb-2.6.22.5-31-ia32-suse10.3-08-01-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/distro/mdb-2.6.23-ia32-fc8-08-02-08.patch
> ftp://ftp.wolfmountaingroup.org/pub/mdb/distro/mdb-2.6.25.14-ia32-fc9-08-02-08.patch
>
> Any additional code fixes I would appreciate being placed back into the
> tree, so please sent them back to me if you find the debugger useful.
>
> I commend Keith Owens for his work on kdb and his project is more than
> welcome to share and adapt the code from mdb if it is useful for their
> project. I am certainly looking seriously at using the disassembler in
> kdb for mdb, with my enhancements rolled into it.
>
> Jeffrey Vernon Merkey
>
>
Well I think given the fact that kdb is not accepted by Linus, there
is little possibility that mdb will be included in mainline kernel.
Though I don't know why kgdb is acceptable.
Regards
Jason Xiao
prev parent reply other threads:[~2008-08-11 10:36 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 17:22 jmerkey
[not found] ` <17494.166.70.238.46.1217784156.squirrel@webmail.wolfmountaingroup.com >
2008-08-03 19:36 ` jmerkey
2008-08-03 20:00 ` Rene Herman
2008-08-04 0:14 ` Josh Boyer
2008-08-04 2:19 ` jmerkey
2008-08-04 13:41 ` Stefan Richter
2008-08-04 14:33 ` jmerkey
2008-08-05 9:41 ` Geert Uytterhoeven
2008-08-05 15:02 ` jmerkey
2008-08-05 15:33 ` Nick Piggin
2008-08-05 15:19 ` jmerkey
2008-08-05 15:45 ` Nick Piggin
2008-08-05 15:32 ` jmerkey
2008-08-05 16:38 ` Nick Piggin
2008-08-05 16:45 ` jmerkey
2008-08-06 19:47 ` Rene Herman
2008-08-05 16:04 ` Chris Friesen
2008-08-05 16:39 ` jmerkey
2008-08-07 20:43 ` Daniel Barkalow
2008-08-07 21:02 ` jmerkey
2008-08-07 21:04 ` jmerkey
2008-08-05 17:21 ` Paul Mundt
2008-08-05 17:10 ` jmerkey
2008-08-06 3:08 ` Andi Kleen
2008-08-06 5:50 ` Nick Piggin
2008-08-07 17:45 ` Christoph Lameter
2008-08-07 17:53 ` jmerkey
2008-08-07 18:08 ` Stefan Richter
2008-08-07 19:10 ` Christoph Lameter
2008-08-07 19:47 ` Jay Lan
2008-08-07 19:34 ` jmerkey
2008-08-08 1:26 ` Vivek Goyal
2008-08-07 20:06 ` Andi Kleen
2008-08-07 20:07 ` Bernhard Walle
2008-08-07 20:09 ` Andi Kleen
2008-08-07 20:11 ` Bernhard Walle
2008-08-07 22:28 ` Keith Owens
2008-08-08 1:15 ` Vivek Goyal
2008-08-08 2:29 ` Andi Kleen
2008-08-08 12:08 ` Cliff Wickman
2008-08-08 12:20 ` Andi Kleen
2008-08-08 13:19 ` jmerkey
2008-08-08 15:06 ` Cliff Wickman
2008-08-08 13:29 ` Vivek Goyal
2008-08-08 14:50 ` Cliff Wickman
2008-08-08 16:57 ` Jay Lan
2008-08-11 12:56 ` Vivek Goyal
2008-08-08 18:03 ` Andi Kleen
2008-08-11 13:02 ` Vivek Goyal
2008-08-11 13:11 ` jmerkey
2008-08-11 13:50 ` Andi Kleen
2008-08-11 16:16 ` jmerkey
2008-08-18 9:12 ` Takenori Nagano
2008-08-08 8:40 ` Nick Piggin
2008-08-06 13:11 ` Bill Davidsen
2008-08-06 13:37 ` Stefan Richter
2008-08-06 13:54 ` Olivier Galibert
2008-08-06 13:45 ` jmerkey
2008-08-06 14:16 ` Nick Piggin
2008-08-06 17:21 ` Jason Wessel
2008-08-06 18:57 ` Andi Kleen
2008-08-07 12:45 ` jmerkey
2008-08-07 15:17 ` Peter Zijlstra
2008-08-07 16:07 ` Andi Kleen
2008-08-07 15:52 ` jmerkey
2008-08-07 17:04 ` Stefan Richter
2008-08-08 0:28 ` Stefan Richter
2008-08-11 10:36 ` jidong xiao [this message]
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=4104961b0808110336x74676e9ane135d2e8c11ccea@mail.gmail.com \
--to=jidong.xiao@gmail.com \
--cc=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®