Re: [libvirt] [PATCH 00/16] snapshot refactoring (incremental backup saga)
On Fri, Mar 22, 2019 at 12:33:25PM +0100, Andrea Bolognani wrote:
On Fri, 2019-03-22 at 11:26 +0000, Daniel P. Berrangé wrote:
> On Fri, Mar 22, 2019 at 07:10:05AM -0400, John Ferlan wrote:
> > On 3/22/19 7:04 AM, Andrea Bolognani wrote:
> > > Michal's patch seems to do the trick: I built from 5e752513d802
> > > and the daemon starts fine even when I have guests with snapshots.
> >
> > Great... That was my first instinct, but would have expected to see this
> > thread causing the issue not the udev one:
>
> The stack trace isn't blaming the udev one. The udev thread is merely the
> most recent, so it appears first. The details of which thread caused
> the crash were not included when stack trace was copied from gdb into
> this mail thread!
Sorry, my bad :(
I blame GDB really. It is very annoying that when you ask it for a stack
trace, it doesn't put a marker on the thread that is associated with the
current caught signal.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|