httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cliff Woolley <jwool...@virginia.edu>
Subject Re: daedalus coredump from 2.0.35c
Date Tue, 09 Apr 2002 19:12:38 GMT

Is this the version with the patched mmap.c, I guess?



On Tue, 9 Apr 2002, Greg Ames wrote:

> I should mention that there were a bunch of seg faults within a minute
> or two, then nothing. NetAnts' web page says it is a download manager
> with several connections each downloading a small piece of the file.
> That may explain why the seg faults were clustered in time.

Well, that's good in a way.  :)


> (gdb) dump_brigade b
>    dump of brigade 0x812c6a8
>    0: bucket=HEAP(0x81311e8), length=207, data=0x8131558
>    1: bucket=TRANSIENT(0x81315b0), length=5, data=0xbfbfe894
>    2: bucket=HEAP(0x81310e0), length=389, data=0x8131138
>    3: bucket=IMMORTAL(0x8131608), length=2, data=0x8083db9
>    4: bucket=IMMORTAL(0x8131660), length=5, data=0x8083dbc
>    5: bucket=EOS(0x8131298), length=0, data=0x0
>    6: bucket=(0x814fefc), length=135590000, data=0x280adea0

Bucket #6 is quite likely the sentinel of another brigade that some stupid
filter copied over on us.  I'd'a sworn we fixed the byterange filter, but
it *is* seeming like a common denominator here.  Which corefile did you
say this was?  I'll try to track it down.

--Cliff

--------------------------------------------------------------
   Cliff Woolley
   cliffwoolley@yahoo.com
   Charlottesville, VA





Mime
View raw message