mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: jmerkey@comcast.net
Cc: linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: kallsyms 2.6.8 address ordering
Date: Thu, 19 Aug 2004 19:33:53 +0100	[thread overview]
Message-ID: <20040819193353.A12168@infradead.org> (raw)
In-Reply-To: <081920041826.25654.4124F0D700037D32000064362200734748970A059D0A0306@comcast.net>; from jmerkey@comcast.net on Thu, Aug 19, 2004 at 06:26:31PM +0000

On Thu, Aug 19, 2004 at 06:26:31PM +0000, jmerkey@comcast.net wrote:
> Yes.
> 
> What would be required?   Source code disclosure to a reviewer.  MDB is platform independent.  and patches in an alternate debugger interface in kdb_main.  In includes **NONE** of SGI's source code or Linux kernel source in the MDB core.  There is an open source section of the debugger with **ALL** modifications to kdb core files disclosed with the debugger modules.  The fact is, I don't even need kdb, but inlcuded it in a mode where folks who wanted to switch between the two debuggers could do so, since a lot of folks wanted to.  I do use the serial interface in kdb, which is the only portion.  I wrote MANOS with this debugger, and all the low level GDT, IDT, etc. hardware stuff is my own, is vastly superior to what's in kdb.   
> 
> DRDOS owns the MDB debugger for Linux now and I maintain it for them -- that's it.  I am certain DRDOS would provide any counter-claims with **FACTS** to assertions we are using any of the kdb code improperly.

So it works with unpatched kernels?


  reply	other threads:[~2004-08-19 18:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 18:26 jmerkey
2004-08-19 18:33 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 22:43 jmerkey
2004-08-20  1:23 ` Horst von Brand
2004-08-19 22:40 jmerkey
2004-08-19 23:11 ` Francois Romieu
2004-08-19 19:27 jmerkey
2004-08-19 19:42 ` David S. Miller
2004-08-19 22:07   ` Julien Oster
2004-08-19 19:24 jmerkey
2004-08-19 19:22 jmerkey
2004-08-19 19:14 jmerkey
2004-08-19 18:10 jmerkey
2004-08-19 18:19 ` Christoph Hellwig
2004-08-19 18:30 ` Rik van Riel
2004-08-19 18:40 ` Richard B. Johnson
2004-08-19 19:00 ` Robin Holt
2004-08-20 11:42   ` Paulo Marques
2004-08-19 20:10 ` Horst von Brand

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=20040819193353.A12168@infradead.org \
    --to=hch@infradead.org \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.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

Powered by JetHome