Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1031981
| From | Bernhard Übelacker <bernhardu@mailbox.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#932250: random segfaults |
| Date | 2020-11-10 11:10 +0100 |
| Message-ID | <B9yL8-5aV-7@gated-at.bofh.it> (permalink) |
| References | <yYJOi-wX-19@gated-at.bofh.it> <yYJOi-wX-19@gated-at.bofh.it> <ykF3r-69x-9@gated-at.bofh.it> <yYJOi-wX-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hello Paul, is it possible to install the package systemd-coredump on the systems showing this crash? Then after the next crash in the output of 'journalctl --no-pager' should the segfault appear followed by a backtrace that you could forward to this bug. This should clarify which function calls lead to the crash. More information on improving that information additionally are here: https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#932250: random segfaults Bernhard Übelacker <bernhardu@mailbox.org> - 2020-11-10 11:10 +0100
Bug#932250: random segfaults Paul Kerry <p.kerry@sheffield.ac.uk> - 2020-11-10 11:40 +0100
Bug#932250: random segfaults Salvatore Bonaccorso <carnil@debian.org> - 2020-11-13 10:30 +0100
csiph-web