[Git][glibc-team/glibc][sid] debian/compat, debian/control.in/main, debian/rules.d/debhelper.mk: increase...
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 05cf9c21 by Aurelien Jarno at 2022-08-22T23:36:23+02:00 debian/compat, debian/control.in/main, debian/rules.d/debhelper.mk: increase debhelper compat to 13, the declarative way, and replace calls to dh_systemd_enable and dh_systemd_start by dh_installsystemd. - - - - - 5 changed files: - debian/changelog - − debian/compat - debian/control - debian/control.in/main - debian/rules.d/debhelper.mk View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/05cf9c219de016c59e34b28e410c7888e7842245 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/05cf9c219de016c59e34b28e410c7888e7842245 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][glibc-2.35] Fix starting static binaries with stack protection enabled
Samuel Thibault pushed to branch glibc-2.35 at GNU Libc Maintainers / glibc Commits: 55ca6703 by Samuel Thibault at 2022-08-22T20:35:20+00:00 Fix starting static binaries with stack protection enabled * debian/patches/hurd-i386/git-static-pie.diff - - - - - 3 changed files: - debian/changelog - + debian/patches/hurd-i386/git-static-pie.diff - debian/patches/series View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/55ca6703a20089dda075b31341dfe7ce5b905c93 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/55ca6703a20089dda075b31341dfe7ce5b905c93 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] debian/patches/hurd-i386/git-cond-destroy.diff: Fix tst-cond20
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 79a251c1 by Samuel Thibault at 2022-08-22T20:29:59+00:00 debian/patches/hurd-i386/git-cond-destroy.diff: Fix tst-cond20 - - - - - 3 changed files: - debian/changelog - + debian/patches/hurd-i386/git-cond-destroy.diff - debian/patches/series View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/79a251c196d855b5e4e8bcd01d6f408becc79905 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/79a251c196d855b5e4e8bcd01d6f408becc79905 You're receiving this email because of your account on salsa.debian.org.
Re: ld-linux-x86-64 core file SIGSEGV
On 22/08/2022 19:59, Aurelien Jarno wrote: > Hi, > > On 2022-08-22 11:16, Jonny Grant wrote: >> Hello >> >> Just wondering if any ideas why libc6-amd64-dbgsym doesn't seem to contain >> any debug symbols for /lib64/ld-linux-x86-64.so.2 ? > > It does contain the symbols for libc6-amd64, which means you run this > binary from a i386 (or x32) system. Is it really your case? > > In the likely case you run this from an amd64 system, you want to > install libc6-dbg instead (and get rid of libc6-amd64-dbgsym and > libc6-amd64). Hi Aurelien Many thanks for your reply with that tip Kind regards, Jonny
Re: ld-linux-x86-64 core file SIGSEGV
Hi, On 2022-08-22 11:16, Jonny Grant wrote: > Hello > > Just wondering if any ideas why libc6-amd64-dbgsym doesn't seem to contain > any debug symbols for /lib64/ld-linux-x86-64.so.2 ? It does contain the symbols for libc6-amd64, which means you run this binary from a i386 (or x32) system. Is it really your case? In the likely case you run this from an amd64 system, you want to install libc6-dbg instead (and get rid of libc6-amd64-dbgsym and libc6-amd64). Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
[Git][glibc-team/glibc][sid] Some XFAILs were actually not upstreamed
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 43916f8b by Samuel Thibault at 2022-08-22T14:31:30+00:00 Some XFAILs were actually not upstreamed - - - - - 1 changed file: - debian/testsuite-xfail-debian.mk View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/43916f8b2942868023aa26d9e6bf0f727dee7532 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/43916f8b2942868023aa26d9e6bf0f727dee7532 You're receiving this email because of your account on salsa.debian.org.
Re: ld-linux-x86-64 core file SIGSEGV
Hello Just wondering if any ideas why libc6-amd64-dbgsym doesn't seem to contain any debug symbols for /lib64/ld-linux-x86-64.so.2 ? I wanted to debug a crash Kind regards Jonny On 22/08/2022 07:41, Florian Weimer wrote: > * Jonny Grant: > >> Hello >> I have a core file from a crash in glibc's ld.so >> >> Couldn't reproduce it. Was just wondering if there was any useful info >> I could extract to identify which function it crashed in? > >> I can see the backtrace using 'bt' command. >> I can see the assembly using 'layout asm' >> >> >> Core was generated by `/lib64/ld-linux-x86-64.so.2 >> /usr/lib/vmware/lib/libvmware-modconfig.so/libvmwar'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 0x7fac33ccb540 in ?? () >> (gdb) bt >> #0 0x7fac33ccb540 in () >> #1 0x7fac33ccea00 in () >> #2 0x7fac33ccdfa0 in () >> #3 0x7fac33c496b0 in () >> #4 0x7fac33c49bf0 in () >> #5 0x7fac33c4a130 in () >> #6 0x7fac33ccd000 in () >> #7 0x7fac33c4a670 in () >> #8 0x7fac31cdf310 in () at >> /usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so >> >> >> installing libc6-amd64-dbgsym doesn't show any more > > Sometimes it's possible to get better backtraces by loading the symbol > table for the name program using “file”, running ld.so and the program > under the debugger, or both. I've got a request open with our GDB > developers to improve debugging with an explicit ld.so invocation, but > so far, it's a known issue. > > Thanks, > Florian >
