RE: a exit() bug in multithreaded program

[Dan Kegel]

Looks like it was cut off.  The URL continues
with "03-May/msg00066.html".
The full URL is
https://listman.redhat.com/archives/phil-list/2003-May/msg00066.html
The page to subscribe is at 
https://listman.redhat.com/mailman/listinfo/phil-list
- Dan

-----Original Message-----
From: SHEN Feng
To: Dan Kegel
Cc: address@hidden; MAEDA Naoaki
Sent: 29.05.2003 18:31
Subject: Re: a exit() bug in multithreaded program

Hi Dan,
    Our system is Red Hat 9 on IA32.
    https://listman.redhat.com/archives/phil-list/20
    This URL contains errors. I cannot find the problem you mentioned.
  
B.R.
                  SHEN Feng

----- Original Message ----- 
From: "Dan Kegel" <address@hidden>
To: "SHEN Feng" <address@hidden>
Cc: <address@hidden>; "MAEDA Naoaki" <address@hidden>
Sent: Friday, May 30, 2003 1:17 AM
Subject: Re: a exit() bug in multithreaded program


> SHEN Feng wrote:
> > In the function exit(), the global variable __exit_funcs isn't
protected
> > for multithreaded program. But __exit_funcs at __new_exit_fn() in
> > cxa_atexit.c is protected by a lock. The function __new_exit_fn() is
> > called by atexit() and on_exit(). So __exit_funcs at exit() should
also
> > be protected by the lock. It’s a bug.
> >
> > I have had a test on this function. The test function exit_test.c
and
> > the result file exit_test_result_redhat.log are attached. From them
we
> > can concluded that the exit() may be unsafe in multithreaded
program.
> 
> Hi Feng,
> you didn't mention which version of glibc or the operating system;
> that makes it a bit harder to help.
> 
> Assuming you're using the version shipped with Red Hat 9,
> this sounds vaguely related to a problem mentioned on the NPTL mailing
list:
> https://listman.redhat.com/archives/phil-list/20
> You might want to subscribe there; see
> https://listman.redhat.com/mailman/listinfo/phil-list
> - Dan
> 
>