[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Availability of kdb
On Wed, 6 Sep 2000, Alan Cox wrote:

> In many ways good crash dump tools and tracebacks (oopses do not count) are
> the valuable bit - remote gdb happens to be a passable crash dump tool

if you're lucky and can analyse the crash online, maybe. but offline
crash dump analysis is the only option for a mission critical system with
terabytes of attached data... you know, those problems you can never
reproduce in testing, but are guaranteed to happy monday morning when
everyone comes back from the weekend and slams the net. as much as i
dislike solaris and veritas, i have to give their engineers credit for
working from 6Gb crash dumps and responding with patches a few days later.

(i'd put the word "enterprise" up there, but too many folks think it's
just marketing... until they actually have to deal in that realm :)

ObDebuggerReligion: i favour debuggers. i frequently learn how code is
structured by walking into it with a debugger... i do this even when i
want to add features rather than fix bugs. a debugger is a tool, it can't
think for you; you're still in control.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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