pogma

So I was always annoyed by the way dlcompat
used to just leak. Then one day a couple of months ago, I said to myself “Hey, just add a call to atexit(3) and put in some cleanup code”.
I figured that it would be safe to deallocate everything then, after all we are in exit(), nothing could possibly call dlopen/dlclose/dlerror/dlsym from there right?

WRONG!

I discovered today that it is indeed possible to call dl functions after exit() has been called.
C++ static destructors can be called after I do my cleaning in dlcompat_cleanup. So, exit calls dlcompat_cleanup which deallocates all it’s malloc’d blocks and the pthread locks etc. exit then proceeds to call
the c++ static destructors which call dlclose, at which point dlcompat barfs all kinds of ugly stuff before it dies rather vocally.

So now I guss I have to go patch dlcompat to leak again. Sometimes it is better to leak
than have something squat on your head and do a big poop.

I am now a libtool co-maintainer.
That is pretty cool. I get a commit if approved by another maintainer or if 72 hours pass
without comment on my patches. Beats the hell out of waiting for what certainly feels like forever for someone to commit my patches.

On the downside, of course, is that I am now one of the people that patch submitters
are going to be mad at for not committing their patches as soon as they post them to the mailing list.
I used to think that it was a relatively easy process, but it is a little harder than
I originally thought.

Got to make sure the patch does what it says, try your best to ensure it breaks nothing,
and, of course, test the thing on as many systems as possible.

No wonder it took forever for my patches to be applied.