inn 2.4.3 segfaults in certain incoming.conf situations
Julien ÉLIE
julien at trigofacile.com
Thu Jun 28 06:47:11 UTC 2007
En réponse à Bill Davidsen :
> Whoever wrote it should learn how to use /*comments*/
> to make it more maintainable.
It is very old.
Revision 281 (1998/01/18)
« Mega inn.status and hosts.nntp patch ».
The code was the same as it is now.
> There's a possible bug in the code below, after "free(groups)"
By the way, in my daily Usenet report, I noticed that I have
two lines in my errlog:
*** glibc detected *** free(): invalid next size (fast): 0x080c8250 ***
*** glibc detected *** free(): invalid next size (fast): 0x080c8250 ***
(I do not understand why there are *only* two lines)
--
Julien
« C'est une souricière, ils sont faits comme des rats ! » (Astérix)
More information about the inn-workers
mailing list