Nginx 1.3.10 Segfault

[ビリビリⅤ]

confirmed, only 1.3.10 have this bug, 1.3.9 is no problem.


2013/1/5 ビリビリⅤ <orz at loli.my>

> I have checking 1.3.9 for this bug. I have confirmed 1.3.8 haven't this
> bug.
>
>
> 2013/1/5 Valentin V. Bartenev <vbart at nginx.com>
>
> On Saturday 05 January 2013 08:30:57 ビリビリⅤ wrote:
>> > patched is still throw the same segfault. I think may be cause by 1.3.9
>> > feature:
>> >
>>
>> Do you mean that the problem also occurs on 1.3.9?
>>
>> >  *) Feature: the $request_time and $msec variables can now be used not
>> >        only in the "log_format" directive.
>> >
>> >
>>
>> No, this change have nothing to do with the access log module.
>>
>> Are you sure that you applied patch well? Enabling buffered logs should
>> also fix
>> the problem. See: http://nginx.org/r/access_log ("buffer" or "gzip"
>> parameters).
>>
>>
>>  wbr, Valentin V. Bartenev
>>
>> --
>> http://nginx.com/support.html
>> http://nginx.org/en/donation.html
>>
>> _______________________________________________
>> nginx-devel mailing list
>> nginx-devel at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20130106/e9c110f5/attachment.html>