atexit considered harmful?

问题

Are there inherent dangers in using atexit in large projects such as libraries?

If so, what is it about the technical nature behind atexit that may lead to problems in larger projects?

回答1:

The main reason I would avoid using atexit in libraries is that any use of it involves global state. A good library should avoid having global state.

However, there are also other technical reasons:

1. Implementations are only required to support a small number (32, I think) of atexit handlers. After that, it's possible that all calls to atexit fail, or that they succeed or fail depending on resource availability. Thus, you have to deal with what to do if you can't register your atexit handler, and there might not be any good way to proceed.

2. Interaction of atexit with dlopen or other methods of loading libraries dynamically is not defined. A library which has registered atexit handlers cannot safely be unloaded, and the ways different implementations deal with this situation can vary.

3. Poorly written atexit handlers could have interactions with one another, or just bad behaviors, that prevent the program from properly exiting. For instance, if an atexit handler attempts to obtain a lock that's held in another thread and that can't be released due to the state at the time exit was called.

回答2:

Secure CERT has an entry about atexit when not used correctly:

ENV32-C. All atexit handlers must return normally

https://www.securecoding.cert.org/confluence/display/seccode/ENV32-C.+All+atexit+handlers+must+return+normally

来源：https://stackoverflow.com/questions/17350308/atexit-considered-harmful