lkml.org 
[lkml]   [1999]   [May]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.8_ikd1.bz2
Hi,

IMVHO, you should merge Scott Lurndal's built-in kdb since, to the best of
my knowledge, the intention is to maintain IKD separately. There is no
doubt that both IKD and Scott's kdb are extremely useful and
technically brilliant pieces of software but they are
also rather intrusive, i.e. one can seriously argue against having them
on a production machine. As for David Grothe's
remote gdb support it is not more intrusive than the equivalent support on
other architectures which is already included in the official kernel so I
think it should be included in the official kernel, which was already
suggested by David to Linus.

Regards,
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.aivazian.demon.co.uk

On Wed, 12 May 1999, Andrea Arcangeli wrote:

> I released a new 2.2.8_ikd1. As usual it has the kernel tracer, print-eip,
> memleak detector, stack overflow meter/detector, semaphore deadlock
> oopser, NMI deadlock oopser, kernel debugger etc....
>
> About the debugger, now there should be an updated kernel debugger by
> David Grothe <dave@gcom.com> somewhere, and I seen also a debugger from
> SGI. Which is the better one to merge in the ikd tree?
>
> Andrea Arcangeli
>
>




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.075 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site