Ben Reed’s employer just closed their doors, so he’s looking for a job..
Okay, I’m getting a several hundred messages a day to my sourceforge email address, most of them are neither spam, nor virii, but are bounces of spam and virii. I really wish people would simply delete any virii they find in incoming mail. If it is a virus it has a forged “from” header, simple as that, do not bounce the darn thing.
In good news, I am now 5 months without a smoke, but if you fools keep bouncing spam and virii back to me I may have to send you free packages of cigarettes.
New Mobile Phone
Got a new phone! It takes movies 
It does other stuff too, of course.
You can talk on it and stuff, you can take pictures. It does videophone
type things.
I like it.
The movie is of Jessica, of course. Took it last night with my phone.
Wow! I surprised myself. I didn’t really believe that I could give up smoking for more than a day or two,
having been a smoker most of my life. I smoked for 22 years, which I figure means I had about 200,000 cigarettes,
spent nearly U.S. $20,000 and shortened my life.
We’ll see if I can continue, I still spend a large amount of time thinking about smoking, but am able to concentrate
for more than 5 minutes at a time again (I couldn’t for a while, just kept thinking about how much I wanted to smoke).
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.
Well it has taken a little while, but I finally have a working Mac OS X 10.2 install again.
Time to get fink up to date and update my packages this week, then with a bit of luck
I will be able to help out drm and jfm with the gcc-3.3 fink updates.
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.