public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jmerkey <jmerkey@utah-nac.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: 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 00:44:57 -0600	[thread overview]
Message-ID: <42BBABE9.7010300@utah-nac.org> (raw)
In-Reply-To: <42BBD4A1020000780001D4D1@emea1-mh.id2.novell.com>

Jan Beulich wrote:

>>1. No back trace
>>    
>>
>
>You're the second one to mention this, and I wonder where you take this from.
>  
>
Check the version binaries on NovellForge. Didn't work. Suse Linux perhaps?

>  
>
>>2. Doesn't run standalone fully embeded in the kernel
>>    
>>
>
>What do you mean with 'fully embedded'? As long as the agents aren't compiled as modules, everything's right in the kernel (of course, not the mainline one, but that's same as for kdb and kgdb).
>  
>

Right.

>  
>
>>3. Not fully open source (since it's not embeded in the kernel)
>>    
>>
>
>What has embedding things in the kernel to do with being open source?
>  
>

Debuggers need to be open source to work on Linux (socially work, not 
technically). They also need to use kdb
and gdb as a base, so you can have one patch that runs on all the kdb 
versions for the kernels. Then you can use kdb
and let it do all the interfacing beneath you and leverage KDB and the 
porting effort there. Hook kdb() and traps.c
for events to userspace.


>  
>
>>5. No advanced recursive descent parser for conditional breakpoints
>>    
>>
>
>Where've you seen this? What functionality does the parser miss?
>  
>

Your architecture is event based, but there's no source code to change 
this, just a white paper. How do I know a conditional
breakpoint is running real time when it triggers. No source code, no 
interest.... Social Problem.

There is ****NO**** commerical debugger business on Linux. I don't agree 
that the GPL contaminates most
kernel modules, but a kernel debugger is one exception, because it has 
to include key kernel header files and truly is
an "integrated" component (at least a decent one is).

If you want to promote an interesting project and make no money off of 
it, open source your debugger, put it on KDB
as a base, and lots of folks will use it. We tried the whole kernel 
debugger product thing, and there are actual legal
issues if you choose not to open source it. File Systems, drivers, etc. 
-- not the case. Kernel debugger is the case.

:-)

Jeff


>Jan
>
>
>  
>


  reply	other threads:[~2005-06-24  8:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  7:38 Novell Linux Kernel Debugger (NLKD) Jan Beulich
2005-06-24  6:44 ` jmerkey [this message]
2005-06-24  8:26 ` Keith Owens
2005-06-24 12:02   ` Rik Van Riel
2005-06-27  6:46     ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 18:03 Clyde Griffin
2005-06-24  6:29 Jan Beulich
2005-06-23 22:54 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
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

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=42BBABE9.7010300@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 \
    /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