> Samuel Thibault writes:
>
>> jann...@gnu.org, le sam. 16 nov. 2024 17:33:08 +0100, a ecrit:
>
>>> git-fault-64bit.diff
>>> git-intr-msg-clobber.diff
>>
>> You do want these two. See the bug-hurd mailing list logs for the
>> details, basically git-intr-msg-clobber.diff is really a requirement,
>> otherwise e.g. $() shell replacement don't work properly.
Hmm. I found that using git-intr-msg-clobber.diff, gdb no longer works
for me, I get:
--8<---------------cut here---------------start------------->8---
Current directory is
/ssh:root@childhurd1:/tmp/guix-build-findutils-boot0-4.9.0.drv-0/findutils-4.9.0/gnulib-tests/
GNU gdb (GDB) 15.2
[..]
Reading symbols from test-setsockopt...
(gdb) b main
Breakpoint 1 at 0x4011ba: file test-setsockopt.c, line 37.
(gdb) r
Starting program:
/tmp/guix-build-findutils-boot0-4.9.0.drv-0/findutils-4.9.0/gnulib-tests/test-setsockopt
[bogus thread id 1 exited]
Handling event, msgid = 2400: (ipc/mig) server type check failure
--8<---------------cut here---------------end--------------->8---
and after that, nothing works anymore. I found
<https://lists.debian.org/debian-hurd/2024/07/msg00063.html>
talking about save_data in relation to the clobber thing. Has anyone
verified that gdb still works with this patch?
Or could it be that I also need
<https://salsa.debian.org/glibc-team/glibc/-/blob/027f94215a633cbf53794d4b48675fde36706e35/debian/patches/hurd-i386/local-intr-msg-clobber.diff>
for gdb to work again? I'm currently stuck on gnulib's test-setsockopt
hanging (it works on debian).
Greetings,
Janneke
--
Janneke Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
