Status of ticket #105?

["Vilhelm K. Vardøy"]

Vilhelm K. Vardøy wrote:
> Dag-Erling Smørgrav wrote:
>> The first stack trace shows an assertion failure in EXP_TTLchange() and
>> is probably related  to url.purge [...]
>>
>> The attached patch should prevent the first case from reoccurring.  
> 
> Thanks.   We'll apply the patch today, but there won't be any real 
> traffic on the site until tonight.
> 

The patch obviously fixed the one issue, thanks.  However, varnishd 
stilled died over 100 times within 2 hours on the last "run" (monit 
sends a email for each time it has to start varnish), this time I 
discovered another one:

(gdb) bt
#0  0x2817becb in kill () from /lib/libc.so.6
#1  0x280b32d2 in raise () from /usr/lib/libthr.so.2
#2  0x2817ab78 in abort () from /lib/libc.so.6
#3  0x2809eaf6 in lbv_assert (func=0x8068c49 "ev_schedule_one",
     file=0x8068cb2 "mgt_event.c", line=450,
     cond=0x8068de8 "evb->lpfd < evb->npfd", err=9) at assert.c:58
#4  0x0805e51c in ev_schedule_one (evb=0x8075040) at mgt_event.c:450
#5  0x0805e5c9 in ev_schedule (evb=0x8075040) at mgt_event.c:344
#6  0x0805c301 in mgt_run (dflag=0, T_arg=0xbfbfe7b0 "\001") at 
mgt_child.c:409
#7  0x08063dd2 in main (argc=17, argv=0xbfbfed3c) at varnishd.c:540


I'm not sure that this is the cause in all cases(/crashes), since the 
core-file gets overwritten for each time (I only have the core-file from 
the last time it crashed). Is there a simple way to keep all core-files?

-- 
Vilhelm.