[Crash-utility] Question for LKCD maintainers

[Dave Anderson]

This works for me, and is what I'm going with unless
anybody objects.  I'm returning -1 instead of calling
abort(), and the error message is now CRASHDEBUG(1)
because it tends to spew way too many of them over the
course of one readmem() call, not to mention that the
contents of the message are of little use to anybody
but an LKCD developer.  I'm really only interested in
knowing that the dumpfile access failed, and this patch
accomplishes that without shutting down the crash session.

Dave



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lkcd.patch
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20071116/c0306616/attachment.ksh>