my pho e
Sent from my iPhone
On 24-Sep-2022, at 03:21, Aurelien Jarno wrote:
Hi,
On 2022-09-23 21:28, Bernhard Übelacker wrote:
On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath wrote:
Package: libc6
Version: 2.34-8
I upgraded libc6 to latest released 2.35-1
Module ld
On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath wrote:
Package: libc6
Version: 2.34-8
I upgraded libc6 to latest released 2.35-1
Module ld-linux-x86-64.so.2 with build-id
a03c3b14d371da908a3f22007b3f0c73d1f9f634
Module libc.so.6 with build-id
Dear Maintainer,
encountered again such a crash of a bash that was started
while the old libc6 was installed, then installed a libc6 update,
and then the "old" bash crashed after a tab completion.
libc6:amd64 (2.30-8, 2.31-3)
bash:amd64 (5.0-6, 5.0-7)
Kind regards,
Bernhard
$ cp log*** stack
Dear Maintainer,
I could reproduce the crash now in an minimal unstable VM with the
given config and the command line from the coredumpctl output.
It seems that the function conf_parse_line is not prepared
for missing quotation marks for the argument in the section head [1].
Therefore, if quotes
Hello Miriam,
thanks for the backtraces, just the one from "coredumctl gdb" is enough.
Have you by any chance a file "/etc/nfsmount.conf" at this system?
If there are no secrets inside, could you attach that too?
Kind regards,
Bernhard
Hello Miriam,
if possible, you could install the additional package
systemd-coredump. Then in the output of 'journalctl --no-pager'
at the bottom should the known 'segfault at' line appear.
This and the following lines at that time would be of interest.
This would get better if the additional
Dear Maintainer,
sorry, did attempt to output the build-id unconditionally,
fixed in attached patch version.
Kind regards,
Bernhard
>From 0a4a73d4eeaa45acdbeb6ea8fea878e134cbc11b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=
Date: Wed, 11 Dec 2019 19:56:39 +0100
Subject:
Dear Maintainer,
while I was at it, I attempted to change the output to
deliver the before mentioned information for addr2line too.
Attached is a improved patch, that would now output following:
Backtrace:
[0x55f317f9175b] main at
/usr/share/doc/libsoxr-dev/examples/3-options-input-fn.c:79
Package: libc-bin
Version: 2.29-3
Severity: wishlist
Tags: upstream patch
Dear Maintainer,
since upstream commit in 2012 [1] the function __backtrace_symbols_fd
seems to outputs in one of this formats:
program(+)[]
program(function+)[]
Therefore the /usr/bin/catchsegv cannot find the
Dear Maintainer,
this looks like a matching upstream bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=18035
Kind regards,
Bernhard
10 matches
Mail list logo
