[Bug 1099886] snapperd segfault in destructor
http://bugzilla.suse.com/show_bug.cgi?id=1099886 http://bugzilla.suse.com/show_bug.cgi?id=1099886#c8 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jnelson-suse@jamp | |oni.net) --- Comment #8 from Stefan Hundhammer <shundhammer@suse.com> --- As far as I can tell, this is the message that should have been logged: https://github.com/openSUSE/snapper/blob/master/snapper/Snapper.cc#L136 There is nothing fancy about it; there are no C++ objects involved anywhere in the logging logic of snapper that might be destroyed in an unfortunate order. AFAICS, it's all static functions that don't go away because an object is destroyed. Depending on command line parameters, snapperd either logs to stdout (if started with -s or --stdout), or it uses the default logger which should log to /var/log/snapper.log . https://github.com/openSUSE/snapper/blob/master/snapper/Logger.cc#L138 Can you check if you see messages in /var/log/snapper.log, and if yes, attach that file? Maybe this gives more insights. Also, please check what exact versions of snapper you have on your system: sudo rpm -qa | grep snapper -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com