jeudi 22 octobre 2020

C++ shared object initialization constructor destructor

I'm working on a Shared Object compiled with g++ that serves as a logging API. I've written a little utility to exercise the library, but I've found that the shared object constructor/destructor are called every time the program starts and exits. I'd like to be able to maintain the state of any variables/objects in the .so file, even if there are no active applications linked. Is there a mechanism for accomplishing this?

Aucun commentaire:

Enregistrer un commentaire