From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Christoph Hellwig <hch@vger.timpanogas.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Hari Gadi <HGadi@ecutel.com>,
linux-kernel@vger.kernel.org
Subject: Re: module (kernel) debugging
Date: Thu, 21 Mar 2002 17:33:11 -0700 [thread overview]
Message-ID: <20020321173311.A25805@vger.timpanogas.org> (raw)
In-Reply-To: <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com> <E16oBVq-0006Z6-00@the-village.bc.nu> <20020321163015.A25688@vger.timpanogas.org> <20020321232955.A20289@infradead.org>
On Thu, Mar 21, 2002 at 11:29:55PM +0000, Christoph Hellwig wrote:
> On Thu, Mar 21, 2002 at 04:30:15PM -0700, Jeff V. Merkey wrote:
> >
> > One more:
> >
> > MDB - source level kernel debugger.
>
> Where?
www.kdebug.com. They are still setting up the website and docs. I
completed the debugger a few weeks ago. I have been working on
it for several months now. If you want a copy to play
with, I can send after I ask permission. I do not own it and was
hired to write it as a work for hire, so it's not open source, it's
a commercial product for Linux.
:-)
Jeff
next prev parent reply other threads:[~2002-03-22 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 22:15 Hari Gadi
2002-03-21 22:58 ` Alan Cox
2002-03-21 23:30 ` Jeff V. Merkey
2002-03-21 23:29 ` Christoph Hellwig
2002-03-22 0:33 ` Jeff V. Merkey [this message]
2002-03-22 0:33 ` Jeff V. Merkey
2002-03-22 0:40 ` Jeff V. Merkey
2002-03-21 23:46 ` Olaf Dietsche
2002-03-22 0:08 ` William Lee Irwin III
2002-03-22 6:36 ` Amit S. Kale
2002-03-22 6:54 ` Andrew Morton
[not found] <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com.suse.lists.linux.kernel>
[not found] ` <E16oBVq-0006Z6-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-03-22 1:26 ` Andi Kleen
2002-03-25 6:48 Rick A. Hohensee
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=20020321173311.A25805@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=HGadi@ecutel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@vger.timpanogas.org \
--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®