Re: Simple project started segfaulting on 7.1-dev - where to report that?
| From: | Derick Rethans | Date: | Mon, 04 Jan 2016 11:53:08 +0000 |
| Subject: | Re: Simple project started segfaulting on 7.1-dev - where to report that? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-89988@lists.php.net to get a copy of this message | ||
On Mon, 4 Jan 2016, Julien Pauli wrote:
> On Fri, Jan 1, 2016 at 8:13 PM, Grzegorz Zdanowski
> <grzegorz129@gmail.com> wrote:
> > Hi!
> >
> > Couple minutes ago I came across segfault in nightly builds of PHP. Normally I will report
> > it at bugs.php.net but environment is little complicated here.
> >
> > - Segfault is only present on TravisCI -> so maybe bug should be reported to Travis-CI?
> > - XDebug is loaded -> it may be a reason of segfault, since it’s also a nightly build
> > - Segfault is produced by some unknown (to me) PhpUnit code -> author of PhpUnit may be
> > helpful here
> > - It originates from PHP core -> maybe bugs.php.net will be the best place? ;)
> >
> > I always try to debug everything as much as possible before reporting, but in this case
> > I’m little puzzled what to do next.
> > Travis-CI build which segfaults can be found here:
> > https://travis-ci.org/kiler129/CherryHttp/jobs/99736122
>
> php.net will not take the bug if Xdebug is activated.
>
> Try to reproduce without XDebug and with just Core activated, then it
> may be PHP related.
That's not necessarily true. A crash with Xdebug has exposed PHP bugs
before, even though it wouldn't crash without Xdebug loaded.
cheers,
Derick