Well no, I don't have any idea for how to reproduce this crash. It started yesterday but I changed nothing on the server. Very odd.
Anything I can do to help further debugging? Anyway, it didn't happen since my last message, so let's pray it stopped :) Thanks! Yo'av 2009/12/28 Alvaro Lopez Ortega <[email protected]> > On 28/12/2009, at 12:54, Yo'av Moshe wrote: > > > Yesterday Cherokee started crushing on me every few hours, so I installed > gdb and got this. > > It started with 0.99.20, but I just upgraded to 0.99.38 and it is still > happening. > > > > Any idea on what's going on? > > After checking the backtrace, I must confess I don't know. I'm glad the > server was able to report the issue though. > > > #8 cherokee_cache_get (cache=0x8579040, key=0x86cf4cc, > ret_entry=0xb75990b8) > > at ../cherokee/list.h:94 > > ret = <value optimized out> > > __func__ = "cherokee_cache_get" > > #9 0x0063b3b9 in iocache_get (iocache=0x0, file=0x8579040, > > info=iocache_stat, fd=0x0, ret_io=0xb7599154) at iocache.c:520 > > ret = <value optimized out> > > entry = (cherokee_cache_entry_t *) 0x0 > > __func__ = "iocache_get" > > #10 0x00cc4949 in cherokee_handler_file_custom_init (fhdl=0x9034888, > > There is an inconsistence in those three entries of the stack-trace. > > You don't know how to trigger this issue, do you? I'd need to reproduce it > locally in order to check where the problem is. Even though the backtrace > pointed me where the problem might be, some finer-grain debugging would be > required. > > -- > Octality > http://www.octality.com/ > > -- Yo'av Moshe
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
