TMI: Loose ends

It's late and I've been too hot on the trail of various bugs (or at least feeling like I was) to write a post, but I don't want to get too much out of the habit of writing.

On Friday I was working on two bugs. The first had to do with changing comm to use classes. The bug wasn't what I thought it was at all. Instead, it was just that the destructors for port_ptrs weren't running at all when the call to port was in a different crate than core. That explained the behavior where the destructor would run if it was called from within the core crate, but not when run from the driver. ( Cut for length )

TMI: Memory leaks and segfaults (or, what compiler writers eat for breakfast)

Also trying to make this brief, since I have work in progress (and am trying not to get sucked back into it tonight! Important when the train home only runs once an hour.)

Yesterday I talked about the bug involving a memory leak in comm, and successfully fixed the first memory leak. Today (well, really, late last night) I isolated the comm unit test that was resulting in a memory leak (exactly one string that was alloc'ed without being freed). ( Cut for length )