----- "urgrue" <urgrue@xxxxxxxxxxx> wrote: > ----- "Jun Koi" <junkoi2004 gmail com> wrote: > >> But I think sometimes we only have the System.map file in hand, > >> without the namelist. Can we do anything with that? Because in many > >> cases only some restricted operations are enough to debug the crashed > >> dump. > > > >The basic design of the crash utility is that it is essentially > >a huge wrapper around the embedded gdb module, taking advantage > >of gdb's allowance of an alternative user interface. So during > > But is it really so that one can not get _any_ useful info from the dump > without the namelist? > Most of the time just the trace is all I need (i.e. that which is > displayed on the console in a panic). That info is not accessible > conveniently because a) the console can only show the last bits of it > and b) I'd rather autoreboot on a panic. > I know I can use netconsole, but it would just be more convenient if I > could read this from the core file easily. I understand, but that's not how the crash utility is designed. You basically want to roll your own utility that doesn't have all the gdb dependencies that crash has. If I'm not mistaken, wasn't there a proposed makedumpfile feature that would just pull the log buffer from a vmcore? Or is that something from the diskdumputils package? I know I've heard talk of it, but I can't recall where. Dave -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
