From: Masami Hiramatsu <mhiramat@redhat.com>
To: jmerkey@wolfmountaingroup.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.27-rc1-git5 2/26] mdb: correct kprobes int3 trap
Date: Wed, 06 Aug 2008 12:51:54 -0400 [thread overview]
Message-ID: <4899D6AA.4000501@redhat.com> (raw)
In-Reply-To: <39379.166.70.238.45.1217950104.squirrel@webmail.wolfmountaingroup.com>
jmerkey@wolfmountaingroup.com wrote:
>> Hi Jeffery,
>>
>> Could you explain what is MDB and how it works?
>
>
> MDB is a kernel debugger that uses the same general architecture
> as the kernel debugger in Netware. Unlike the variants of GNU
> debuggers, MDB is geared towards folks from the intel/microsoft worlds
> who are more accustomed to the old school Intel assembler model and
> not the GNU variant that looks like an angry typewriter cursing at
> the screen (%#*&!, etc.).
Would you have any document about MDB, or project-site url?
I think it is hard for anyone to understand what you like to
do only from these big patchset.
> MDB has some features not yet in this first patch, but I will be adding to
> subsequent patches like the ability to create time based traces of
> execution of code just like an ice does so you can set trigger breakpoints
> (kdb does not, nor kgdb), then go back ad look what happened in windows of
> time, as well as a much easier interface, smaller size, more flexible and
> pluggable command architecture -- a best of all -- it works and does not
> crash every other release or on every third vendors PC architecture like
> kdb does all the time.
Would you have talked with kdb/kgdb people?
Since linux kernel already have kgdb, I think you might better talk
about merging your functionality (and stability) to kgdb, or at least
talk about what part both debugger can share.
> It has been in use by me since 1997, when I wrote it after I left Novell.
> It is mature, hardened, and very stable -- and follows an architecture
> prove in the industry for over 20 years on Netware.
Out of curiously, is there anyone except for you using MDB?
Thank you,
>> And please check your patch style by using scripts/checkpatch.pl.
>> Your cording style seem to be different from linux coding style...
>>
>> Thank you,
>
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2008-08-06 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 6:26 [PATCH 2.6.27-rc1-git5 2/26] mdb: correct kprobes int3 trap jmerkey
2008-08-05 15:33 ` Masami Hiramatsu
2008-08-05 15:28 ` jmerkey
2008-08-06 8:15 ` Stefan Richter
[not found] ` <44714.166.70.238.45.1218029717.squirrel@webmail.wolfmountaingroup.com>
2008-08-06 16:32 ` Stefan Richter
2008-08-06 16:51 ` Masami Hiramatsu [this message]
2008-08-06 19:03 ` jmerkey
2008-08-06 8:40 ` Ananth N Mavinakayanahalli
2008-08-06 13:36 ` jmerkey
2008-08-06 12:21 ` Abhishek Sagar
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=4899D6AA.4000501@redhat.com \
--to=mhiramat@redhat.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