|
From: | Paul Crawford |
Subject: | Re: [Pan-users] Segfaults from recent pan2.git |
Date: | Sun, 02 Feb 2014 23:00:47 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
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.
Regards, Paul
[Prev in Thread] | Current Thread | [Next in Thread] |