Re: [Pan-users] Segfaults from recent pan2.git

[walt]

On 02/02/2014 03:00 PM, Paul Crawford wrote:
> On 02/02/14 22:26, walt wrote: <snip>
>> [New Thread 0x7fffe7fff700 (LWP 21954)] [New Thread 0x7fffe4c98700
>> (LWP 21957)] *** Error in `/home/wa1ter/bin/pan.35b': corrupted
>> double-linked list: 0x0000000017d84e70 ***
>> 
>> That was all there was -- no backtrace was available.
> 
> If you are getting problems relating to corrupted memory that is
> screwing up the debugging, you might want to try linking with the
> "electric fence" library.
> 
> That can lead to an earlier (and cleaner) segfault on memory boundary
> overrun as it uses the machine's virtual memory manager to place each
> allocated block in a separate segment, and it is then enforced by the
> CPU's virtual memory hardware. Hopefully you can trace the cause of
> the bug earlier.

First, git 6e6fd84 has been running all night and is still going, so I'm
confident that git 35bf10f4 is the cause of the crashes.  It's a big patch,
so finding the error is going to be tough.  

I'll try using electric fence.  I've always wondered what it's for, and
now I know, thanks.