This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

exit() fails to take the same lock as __cxa_atexit


Hello all,
exit changes the same global data (e.g.__exit_funcs) that __cxa_atexit changes. Shouldn't it take the same lock?

The problem: I see hanging exit() calls in a program that exits on SIGPIPE and write() == -1 in different threads (exit is not called from a signal context, btw.). The problem seems to go away with _exit().

This is on Linux/ia32 with glibc-2.3.2, but the exit function hasn't changed much.
 
--  Regards 
       Joerg 





Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]