Re: stable innd is segfaulting
colin@marquardt-home.de (Colin Marquardt) wrote:
>* Colin Watson <cjw44@cam.ac.uk> writes:
>> [pid 17274] read(9, "<Yjrd4.10679$Ce.193756@monger.ne"..., 64) = 64
>> [pid 17274] write(17, "335\r\n", 5) = 5
>> [pid 17274] select(18, [4 11 13 17], [], NULL, {300, 0}) = 1 (in [17],
>> left {299, 980000})
>> [pid 17274] gettimeofday({947982516, 627961}, NULL) = 0
>> [pid 17274] read(17, "Path: news4.giganews.com!nntp2.g"..., 4095) = 1019
>> [pid 17274] --- SIGSEGV (Segmentation fault) ---
>
>This post is really from someone *not having a clue*, but...
>
>I notice that the `read(...' line above looks like a Message-ID. I
>don't know the RFC for the format, but AFAIR, I have never seen one
>with a Dollar-sign in it. So *maybe* that is wrong: a forbidden (or
>incorrectly handled) Message-ID.
Nah, a $ is (or should be) OK according to RFC 822 - in fact, INN
appears to generate Message-IDs in that format. Thanks for the thought,
though.
--
Colin Watson [cjw44@cam.ac.uk]
Reply to: