Hello!

On Wed, Oct 10, 2012 at 11:05:13PM +0400, Andrey Feldman wrote:

> In attach.
> This one looks interesting.
>
>
> On 10/10/2012 10:30 PM, Andrey Feldman wrote:
> >On 10/10/2012 10:27 PM, Maxim Dounin wrote:
> >>But it's not something I can read (and understand). Obviously
> >>backtrace is invalid/corrupted, and I already named several
> >>possible reasons.
> >
> >I made a new build, will try it now and give you normal bt, i hope:)
> >

> Core was generated by `nginx: worker process '.
> Program terminated with signal 11, Segmentation fault.
> #0 0x000000000040af99 in ngx_vslprintf (buf=0x7fffce908963 "\316\002", last=0x7fffce909130 "", fmt=<value optimized out>,
> args=0x7fffce908910) at src/core/ngx_string.c:254
> 254 while (*p && buf < last) {
> (gdb) bt
> #0 0x000000000040af99 in ngx_vslprintf (buf=0x7fffce908963 "\316\002", last=0x7fffce909130 "", fmt=<value optimized out>,
> args=0x7fffce908910) at src/core/ngx_string.c:254
> #1 0x0000000000406bfe in ngx_log_error_core (level=3, log=0x1bcbf960, err=14, fmt=0x47f5c0 "chmod() \"%s\" failed")
> at src/core/ngx_log.c:120
> #2 0x000000000040e562 in ngx_ext_rename_file (src=0x1bdb2540, to=0x1bdb1c98, ext=0x7fffce909330) at src/core/ngx_file.c:557
> #3 0x000000000045153a in ngx_http_file_cache_update (r=0x1bcbf9e8, tf=0x1bdb2538) at src/http/ngx_http_file_cache.c:938
> #4 0x0000000000446ed6 in ngx_http_upstream_process_request (r=0x1bcbf9e8) at src/http/ngx_http_upstream.c:2686

Ok, thanx, I see what goes on. The patch is indeed wrong, it
broke small HEAD requests. Disregard it.

--
Maxim Dounin
http://nginx.com/support.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx