Hello!

On Wed, Oct 10, 2012 at 05:43:20PM +0400, Andrey Feldman wrote:

> On Wed, Oct 10, 2012 at 3:01 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:
> > Hello!
> >
> > On Wed, Oct 10, 2012 at 02:07:43AM +0400, Andrey Feldman wrote:
> >
> >> Tried your patch, but after few minutes workers starts crashing.
> >> GDB:
> >>
> >> Core was generated by `nginx: worker process '.
> >> Program terminated with signal 11, Segmentation fault.
> >> #0 0x000000000040ab19 in ngx_vslprintf (buf=0x7fff9e5f2785 <Address
> >> 0x7fff9e5f2785 out of bounds>,
> >> last=0x7fff9e5f2f50 <Address 0x7fff9e5f2f50 out of bounds>,
> >> fmt=<value optimized out>, args=0x7fff9e5f2730) at
> >> src/core/ngx_string.c:178
> >> 178 while (*fmt >= '0' && *fmt <= '9') {
> >
> > Strange. What's in backtrace?
>
> Backtrace in attach.

Unfortunately, backtrace is completely unreadable. Not sure if
it's a result of memory corruption, a result of optimization
used, or just a core vs. binary mismatch.


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

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