From: jmerkey <jmerkey@utah-nac.org>
To: Chris Mason <mason@suse.com>
Cc: Jan Beulich <JBeulich@novell.com>,
Christoph Lameter <christoph@lameter.com>,
Clyde Griffin <CGRIFFIN@novell.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: Novell Linux Kernel Debugger (NLKD)
Date: Fri, 24 Jun 2005 09:55:39 -0600 [thread overview]
Message-ID: <42BC2CFB.2010105@utah-nac.org> (raw)
In-Reply-To: <200506240750.03736.mason@suse.com>
Chris Mason wrote:
>On Friday 24 June 2005 00:59, jmerkey wrote:
>
>
>>Jan Beulich wrote:
>>
>>
>>>>It's a GBD replacement and is not fully open source.
>>>>
>>>>
>>>What is not open source in it ()?
>>>
>>>
>>>
>>>>KDB is at present more capable. It has a lot of promise, but it does not
>>>>have the all the architectural
>>>>features necessary to replace either KDB or GDB at present.
>>>>
>>>>
>>>While I never used or saw kdb, I'd be curious about what you immediately
>>>saw missing...
>>>
>>>
>>1. No back trace
>>2. Doesn't run standalone fully embeded in the kernel
>>3. Not fully open source (since it's not embeded in the kernel)
>>4. IA64 doesn't really matter, since IA64 is basically dead anyway
>>5. No advanced recursive descent parser for conditional breakpoints
>>
>>
>
>This is more or less completely inaccurate.
>
>
>
Which one -- more ? or less ?
Jeff
>-chris
>
>
>
>
>
next prev parent reply other threads:[~2005-06-24 17:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 22:54 Novell Linux Kernel Debugger (NLKD) Clyde Griffin
2005-06-23 21:14 ` Parag Warudkar
2005-06-23 23:43 ` Greg KH
2005-06-24 0:24 ` Christoph Lameter
2005-06-24 0:35 ` John W. Linville
2005-06-24 0:17 ` jmerkey
2005-06-24 1:56 ` Rik Van Riel
2005-06-24 0:31 ` jmerkey
2005-06-24 6:21 ` Jan Beulich
2005-06-24 4:59 ` jmerkey
2005-06-24 11:50 ` Chris Mason
2005-06-24 15:55 ` jmerkey [this message]
2005-06-24 18:16 ` Chris Mason
2005-06-24 17:15 ` jmerkey
2005-06-24 19:29 ` Lee Revell
2005-06-24 19:49 ` Christoph Lameter
2005-06-24 0:46 ` Christoph Lameter
2005-06-24 1:36 ` Rik Van Riel
2005-06-24 2:15 ` Keith Owens
2005-06-27 18:14 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 6:29 Jan Beulich
2005-06-24 7:38 Jan Beulich
2005-06-24 6:44 ` jmerkey
2005-06-24 8:26 ` Keith Owens
2005-06-24 12:02 ` Rik Van Riel
2005-06-27 6:46 ` Jan Beulich
2005-06-24 18:03 Clyde Griffin
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=42BC2CFB.2010105@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=CGRIFFIN@novell.com \
--cc=JBeulich@novell.com \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mason@suse.com \
/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