From: Christian B. <chr...@gm...> - 2006-12-05 15:30:24
|
Lloyd Bryant wrote: > Assertion failure (bsched.c:1816) "bs->flags & BS_F_WRITE" > #4 0x080726b3 in bws_write (bs=0x84d8180, wio=0x84b255c, data=0x8326dc0, > len=550) at bsched.c:1816 > #5 0x0808e311 in download_send_request (d=0x86a18ac) at downloads.c:8672 > #6 0x08116545 in socket_connected (data=0x84b2510, source=24, > cond=INPUT_EVENT_W) at sockets.c:1817 > #7 0x082162af in inputevt_dispatch (source=0x86a2a70, condition=G_IO_OUT, > data=0xb6466a00) at inputevt.c:631 > $1 = {last_period = {tv_sec = 33554432, tv_usec = 67108864}, > sources = 0x14000000, stealers = 0x0, > name = 0xc302 <Address 0xc302 out of bounds>, count = 0, type = 24579, > flags = 16777216, period = 67108864, min_period = 335544320, max_period = > 0, > period_ema = 24579, bw_per_second = 0, bw_max = 8413955, > bw_actual = 33556832, bw_last_period = 67108864, bw_last_capped = > 335544320, > bw_slot = 0, bw_ema = 8413955, bw_stolen = 0, bw_stolen_ema = 4, > bw_delta = 16777216, bw_unwritten = 67108864, bw_capped = 335544320, > last_used = 0, current_used = 4, looped = 0} This looks like trash. I've added magic to bsched_t which should catch this. If it's caught early enough, it might show the culprit. -- Christian |