Re: libvirtd segfault

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

 



Op maandag 18 maart 2013 18:19:51 schreef Jiri Denemark:
> On Thu, Mar 14, 2013 at 20:01:16 +0100, AL13N wrote:
> > Op maandag 11 maart 2013 12:59:08 schreef Eric Blake:
> > > On 03/10/2013 09:25 AM, AL13N wrote:
> > > > regarding
> > > > 
> > > > http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
> > > > 
> > > > and
> > > > 
> > > > https://www.redhat.com/archives/libvir-list/2012-December/msg00935.htm
> > > > l
> > > 
> > > There have been several fixes to shutdown since December; can you
> > > reproduce the problem with libvirt 1.0.3?
> > 
> > this is the journalctl output
> > 
> > https://gist.github.com/5164169
> 
> Thanks, but debug logs without a backtrace are not usually very helpful
> in case of a segfault. Could you setup your system to store libvirtd's
> core once it crashes, make sure you have all required debuginfo symbols
> installed, and use gdb to get the backtrace using
> ``thread apply all backtrace'' command?
> 
> Jirka

ok, will try

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]