Comment # 11 on bug 1199425 from Freek de Kruijf

Created attachment 859309 [details]
output of gdb session on terminal with normal backtrace and error in backtrace

Attached is the output of a gdb session. I did put a breakpoint at the exit
"return rc" of the main module. After I continued with step. At a certain
moment I took a backtrace which looked normal. I continued awhile and took
another backtrace, which showed an error in the backtrace.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Maybe this gdb trace gives a clue about the problem. It looks like returning
memory with malloc, which has been returned already.