I built current -dev a couple of days ago, and it seems to be running ok, so I gave linux-5.10.17-rc1 a try (this is a desktop with the orc unwinder, I initially built it with patched 5.10.13 adding the fix Pierre identified).
Now that 5.10.17-rc1 is running, I took a look at dmesg and was shocked to see that unbound had segfaulted. Started it again, segfaulted again. I'm only running unbound as belt and braces (picked that up from a FreeBSD list some time ago). Looking back at the syslog, there have been quite a lot of segfaults in 5.10.13: Some of these are probably from gcc (various exe files such as pr59667.exe and probably nothing to worry about). But I've also got a couple of segfaults from urxvt and gdbus, although I didn't notice any problems related to those. But unbound segfaulted every time it was started. What seems, to me, to be odd about these segfaults is that they all reference the unstripped version of glibc, e.g. Feb 16 01:56:58 origin klogd: [ 515.115052] unbound[1890]: segfault at 100 ip 00007f3fc9406b83 sp 00007fffc68510d0 error 4 in libc-2.33.so.orig[7f3fc9350000+16f000] I had thought that the segfault would reference libc-2.33.so ? Or should I expect it to fault in the .orig version ? Maybe that is something *I'm* doing wrong, -ENO_IDEA. ken@origin ~ $ls -l /lib/libc-2.33* -rwxr-xr-x 1 root root 1995192 Feb 12 00:12 /lib/libc-2.33.so -rwxr-xr-x 1 root root 406584 Feb 12 00:12 /lib/libc-2.33.so.dbg -rwxr-xr-x 1 root root 2394200 Feb 12 00:12 /lib/libc-2.33.so.orig Hmm, at least for unbound Arch and gentoo are ahead of me (I do like it when someone else hits and explains the problem first, but I'm not entirely sure if this is the same problem as I'm seeing). https://github.com/NLnetLabs/unbound/issues/418 https://sourceware.org/bugzilla/show_bug.cgi?id=27343 and suggested fix: https://sourceware.org/pipermail/libc-alpha/2021-February/122364.html which has apparently been committed as: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=c3479fb7939898ec22c655c383454d6e8b982a67 ĸen -- Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout. -- rfc 2324 (1st April 1998) -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
