Am 24.09.22 um 04:24 schrieb Vasudev Kamath:
Hi Aurelien,
Old libc is because I reverted it as some scripts I use and autoconf as well
were breaking.
I assume I have mentioned in report that a downgrade solved crash. If I missed
sorry about that.
Sorry for top posting as I’m replying from my
> Hello Vasudev,
> ok, reverting back would explain reportbug using version 2.34-8.
>
> But was this core taken at a time where all libc packages
> should have been at 2.35-1 ?
> Then I don't understand that "Module" line,
> which shows the build-id from 2.34-8.
Ah sorry I did coredumpctl debug
Package: locales
Version: 2.35-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
While adjusting my localedata patch script to the latest glibc uploads
I discovered a surprising difference in some categories — for example:
(sid-amd64)tglase@tglase:~ $ LC_ALL=C ./tstspc
U+0009
U+000A
U+000B
U+000C
U
Hello, sorry for delayed response, I've managed to collect and analyze a
few coredump files with valid symbols (I installed libc6-dbg and
dpkg-dev, and pointed gdb at Debian's debuginfod server, also used
apt-get source to get the sources for libc6).
It seems there are at least 3-4 distinct pl
I can confirm updating the microcode by installing the intel-microcode
package and rebooting does indeed mitigate this issue. An LXC container
that was previously bricked due to update now starts and seems to behave
fully normally.
[0.00] microcode: microcode updated early to revision
5 matches
Mail list logo
