Re: Bug#1117592: libgc1 fails with pthread_atfork when trying to start on hurd
Samuel Thibault <[email protected]>
| Newsgroups | gmane.linux.debian.ports.hurd |
|---|---|
| Organization | I am not organized |
| Message-ID | <aOZQnc2QwvdQevtr@begin> |
Hello,
Peter Van Eynde, le mer. 08 oct. 2025 08:41:22 +0000, a ecrit:
> GC_thr_init [2] is straight going to abort because CAN_HANDLE_FORK is defined, GC_handle_fork is set but CAN_CALL_ATFORK is not true
It's very odd that CAN_CALL_ATFORK is not set...
#if defined(CAN_HANDLE_FORK) && !defined(CAN_CALL_ATFORK) \
&& !defined(GC_NO_CAN_CALL_ATFORK) && !defined(HOST_TIZEN) \
&& !defined(HURD) && (!defined(HOST_ANDROID) || __ANDROID_API__ >= 21)
/* Have working pthread_atfork(). */
# define CAN_CALL_ATFORK
#endif
It explicitly blacklists the hurd case, but pthread_atfork has been
working since essentially ever there...
Samuel