I have been able to replicate this (on Ubuntu 18.04), but only on some systems. In particular, it didn't fail on a test VM, but did on a larger server.
This commit appears to resolve the issue in my testing: https://github.com/i-scream/libstatgrab/commit/84fd8c38ee4feb0117ed22ab56f6b46661411ec6 And I'd recommend this one too: https://github.com/i-scream/libstatgrab/commit/d4ecd6d440534d0ca14448c602f85fc263f45cb6 See the upstream bug here, which includes for full stack trace with debugging symbols: https://github.com/i-scream/libstatgrab/issues/102 Tim. On Tue, Dec 11, 2018 at 10:54:03PM +0100, Bernhard Übelacker wrote: > Hello Mindaugas Celiesius, > I just tried to reproduce the crash. > Unfortunately it did not crash in my test. > > Therefore I assume the information you provided is not > sufficient for the Maintainer to correct the program. > > Maybe you could install a core dump collector like systemd-coredump. > When another crash happens you can enumerate the recorded crashes by: > coredumpctl list > > And possibly provide the information given by: > coredumpctl gdb > > This output would be even better if saidar-dbgsym from the > debug symbol repositories described in [1]. > > Kind regards, > Bernhard > > [1] https://wiki.debian.org/HowToGetABacktrace -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x6C226B37FDF38D55
