Problem with history - cant fgets after article
sryoungs at bigpond.net.au
Mon Jan 26 05:59:32 UTC 2004
* Russ Allbery <rra at stanford.edu> writes:
> Thank you very much for this! It was extremely helpful.
You're very welcome. Thank you for trying to fix it.
> Steve Youngs <sryoungs at bigpond.net.au> writes:
>> ==8015== Invalid write of size 4
>> ==8015== at 0x8074008: PYartfilter (python.c:122)
>> ==8015== by 0x805EF31: ARTpost (art.c:1873)
>> ==8015== by 0x8069BDE: NCpostit (nc.c:196)
>> ==8015== by 0x806BAC2: NCproc (nc.c:985)
>> ==8015== Address 0x42B81A70 is 0 bytes after a block of size 156 alloc'd
>> ==8015== at 0x40029D7B: malloc (vg_replace_malloc.c:160)
>> ==8015== by 0x80A9B54: x_malloc (xmalloc.c:74)
>> ==8015== by 0x807502A: PYsetup (python.c:680)
>> ==8015== by 0x80694F3: main (innd.c:654)
> I bet this is our arena corruption right here. PYheaditem was also
> being used to store the body and the line count of the message, but
> was only sized to hold all the headers, so we were writing two
> pointers past the end of the array. This has now been fixed in
The Good News: The "can't fgets" error is gone! Woohoo! Thank you
The Bad News: Now I get...
$ rnews -U
rnews: unexpected EOF from server after article
rnews: cant unspool saving to /usr/local/news/spool/incoming/bad/bigpond2e5Q2E
What would you like to see for debugging?
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs at bigpond.net.au>---|
More information about the inn-workers