Part of debug log in reply instead of reply if nginx runs under debugger.

[Andrey Kulikov]

Hi Maxim,

Thanks for a fast reply!

Indeed, I didn't mean to reload configuration. After instructing gdb not to
forward SIGHUP to the process being debugged, everything start to work like
a charm.
Thanks for help!

--
WBR,
Andrey

On 27 June 2016 at 16:34, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Mon, Jun 27, 2016 at 12:30:19PM +0300, Andrey Kulikov wrote:
>
> > I stuck in rather strange situation: if I run nginx under debugger, and
> > request zero-length file it gives me correct reply on first connection.
> But
> > on second connection it reply it output part of debug log (what supposed
> to
> > be written to debug log, but wasn't).
> > At the same time if nginx runs normally (without debugger attached) -
> > everything works as it should.
> >
> > Is is normal situation when nginx runs under debugger?
>
> No, it's not.  Though it looks like you are using 'master_process
> off' and reloading the configuration:
>
> [...]
>
> > master_process off;
>
> [...]
>
> > 2016/06/27 12:24:30 [notice] 32736#0: signal 1 (SIGHUP) received,
> reconfiguring
>
> This can cause various unexpected effects.  If you didn't mean to
> do a reload - check your debugger documentation if it's
> responsible for this.
>
> --
> Maxim Dounin
> http://nginx.org/
>
> _______________________________________________
> 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/20160627/066c1ec5/attachment.html>