Re: [patch] crash on a KVM-generated dump

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- "Sami Liedes" <sliedes@xxxxxxxxx> wrote:

> On Fri, Oct 08, 2010 at 02:48:11PM -0400, Dave Anderson wrote:
> > Can you send me the -d1 output from that dumpfile session with
> > your slirp-patch applied?  Like this:
> > 
> >   # crash -d1 vmlinux dumpfile > /tmp/junk
> >   q
> >   # 
> 
> Of course. Attached.

OK, I was hoping that perhaps it would show up after the cpu and cpu_common
devices, because if that were the case, we could just bail out on reading
any more devices.
 
> I also got this on stderr:
> 
> ------------------------------------------------------------
> WARNING: Because this kernel was compiled with gcc version 4.4.5, certain
>          commands or command options may fail unless crash is invoked with
>          the  "--readnow" command line option.
> ------------------------------------------------------------
> 

That debug message is essentially harmless/useless.  There was a gcc version
in the 3.4.0 timeframe that required the embedded gdb to have --readnow passed
to it in order to gather the required debuginfo data.  It was fixed subsequently,
although I'm not sure in which gcc version.  I should probably at least cap the
message at gcc 4.x.x or something like that.

As far as the slirp device handling, I got this response from Paolo:

> slirp is not supported on RHEL, so I never encountered it.
> 
> Looking at QEMU's source code, SLIRP savevm/loadvm is a mess, and 131 is
> definitely not ok in general because there are several variable-length
> fields.  Looking at it later.
>
> Paolo

Thanks,
  Dave

Attachment: signature.asc
Description: Digital signature

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility

[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux