zero size buf in output(Bug?)

[Maxim Dounin]

Hello!

On Wed, Oct 10, 2012 at 08:07:27PM +0200, Andre Jaenisch wrote:

> 2012/10/10 Maxim Dounin <mdounin at mdounin.ru>:
> > Hello!
> >
> > Unfortunately, backtrace is completely unreadable.
> 
> GooglePlus shows the following as attachment:
> 
> 
> Core was generated by `nginx: worker process                   '.
> Program terminated with signal 11, Segmentation fault.
> #0  0x000000000040ab19 in ngx_vslprintf (buf=0x7fffefda6605 "",
> last=0x7fffefda6dd0 "\020", fmt=<value optimized out>,
> args=0x7fffefda65b0)
>     at src/core/ngx_string.c:178
> 178	            while (*fmt >= '0' && *fmt <= '9') {
> (gdb) bt
> #0  0x000000000040ab19 in ngx_vslprintf (buf=0x7fffefda6605 "",
> last=0x7fffefda6dd0 "\020", fmt=<value optimized out>,
> args=0x7fffefda65b0)
>     at src/core/ngx_string.c:178
> #1  0x000000000040692e in ngx_log_error_core (level=3, log=0x14143930,
> err=14, fmt=0x473e4a "\307", <incomplete sequence \320>)
>     at src/core/ngx_log.c:108
> #2  0x000000000040dfb2 in ngx_conf_set_path_slot (cf=0x14224fe8,
> cmd=<value optimized out>, conf=<value optimized out>)
>     at src/core/ngx_file.c:267
> #3  0x00000000141439b8 in ?? ()
> #4  0x0000000014225850 in ?? ()
> #5  0x00002b87720e8250 in ?? ()
> #6  0x0000000014154770 in ?? ()

[...]

> Not unreadable, but a little bit confusing to me.

I can see gdb output in the attachment, thank you.  :)

But it's not something I can read (and understand).  Obviously 
backtrace is invalid/corrupted, and I already named several 
possible reasons.

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