2012-02-02 I'm doing debugging. My current version of comp(1) aborts if started with an empty draft folder. freeing 0x8a8dc28 at folder_free.c: 33 *** glibc detected *** /home/meillo/src/mmh/uip/comp: double free or corruption (!prev): 0x08a8dc28 *** Only looking closely at the code didn't reveal the failure until now. Hence, I got me a cheat sheet and fired up gdb. Usually I use it only for printing backtraces. Today I wanted to step through the program, line by line. It's not too difficult, actu- ally. But everything looked alright. Then I simply wrote arbitrary values into the specific, dynami- cally allocated array. I even wrote beyond the end. That helped! I could track it down until I could remove or cause the abort by writing or not writing the last element of the array just before freeing it. Not the second-last, not one beyond, but only the last element caused this change. Strange! Tomorrow I'll go for the help of a memory debugger. http://marmaro.de/lue/ markus schnalke