Re: pthread_atfork vs dlopen/dlclose

2025-04-10 Thread Corinna Vinschen via Cygwin
On Apr 10 11:03, Jeremy Drake via Cygwin wrote: > On Thu, 10 Apr 2025, Corinna Vinschen via Cygwin wrote: > > > > It seems glibc takes care of this implicit deregistration in > > > __cxa_finalize, after calling __cxa_atexit functions, it unregisters any > > > at_quick_exit or pthread_atfork callba

Re: pthread_atfork vs dlopen/dlclose

2025-04-10 Thread Jeremy Drake via Cygwin
On Thu, 10 Apr 2025, Corinna Vinschen via Cygwin wrote: > > It seems glibc takes care of this implicit deregistration in > > __cxa_finalize, after calling __cxa_atexit functions, it unregisters any > > at_quick_exit or pthread_atfork callbacks from the DSO being unloaded. > > > > https://sourcewar

Re: pthread_atfork vs dlopen/dlclose

2025-04-10 Thread Corinna Vinschen via Cygwin
On Apr 9 23:32, Jeremy Drake via Cygwin wrote: > On Wed, 9 Apr 2025, Jeremy Drake via Cygwin wrote: > > > On Thu, 10 Apr 2025, Kevin Schnitzius via Cygwin wrote: > > > > > On Wednesday, April 9, 2025 at 06:54:34 PM EDT, Jeremy Drake via Cygwin > > > wrote: > > > > > > > The recent issue with pt

Re: pthread_atfork vs dlopen/dlclose

2025-04-09 Thread Jeremy Drake via Cygwin
On Wed, 9 Apr 2025, Jeremy Drake via Cygwin wrote: > On Thu, 10 Apr 2025, Kevin Schnitzius via Cygwin wrote: > > > On Wednesday, April 9, 2025 at 06:54:34 PM EDT, Jeremy Drake via Cygwin > > wrote: > > > > > The recent issue with pthread_atfork handlers reminded me of a scenario > > > that I kno

Re: pthread_atfork vs dlopen/dlclose

2025-04-09 Thread Jeremy Drake via Cygwin
On Thu, 10 Apr 2025, Kevin Schnitzius via Cygwin wrote: > On Wednesday, April 9, 2025 at 06:54:34 PM EDT, Jeremy Drake via Cygwin > wrote: > > > The recent issue with pthread_atfork handlers reminded me of a scenario > > that I know glibc handles, but it seems that Cygwin does not.  Test case: >

Re: pthread_atfork vs dlopen/dlclose

2025-04-09 Thread Kevin Schnitzius via Cygwin
On Wednesday, April 9, 2025 at 06:54:34 PM EDT, Jeremy Drake via Cygwin wrote: > The recent issue with pthread_atfork handlers reminded me of a scenario > that I know glibc handles, but it seems that Cygwin does not.  Test case: <... code that loads a shared lib, registers some functions in sha