On Mon, 2019-12-23 at 23:36 +0100, Julian Andres Klode wrote: > The coredump should be useless, as this sounds like a memory > corruption issue, which would need debugging in valgrind to find the > first illegal write.
I can make available any of the following, should it help: Architecture, CoreDump, ExecutablePath, ProblemType, ProcEnviron, Signal, Date, ExecutableTimestamp, ProcCmdline, ProcMaps, Uname, DistroRelease, _LogindSession, ProcCwd, ProcStatus -- Kip Warner -- Senior Software Engineer OpenPGP signed/encrypted mail preferred https://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
