# Simple project started segfaulting on 7.1-dev - where to report that?

- Thread: https://externals.io/message/89950
- Original archive: https://news-web.php.net/php.internals/89950
- Started by Grzegorz Zdanowski on 2016-01-01T19:13:54+00:00
- Messages: 4
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #89950 — Grzegorz Zdanowski — 2016-01-01T19:13:54+00:00

URL: https://externals.io/message/89950#89950

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

--
Best regards.
Grzegorz Zdanowski

---

## #89984 — Julien Pauli — 2016-01-04T08:49:07+00:00

URL: https://externals.io/message/89950#89984 · In reply to: #89950

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.


Julien.Pauli

---

## #89987 — Derick Rethans — 2016-01-04T11:52:21+00:00

URL: https://externals.io/message/89950#89987 · In reply to: #89950

> 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?

Travis is ZTS - so that might be a difference there.

> - 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? ;)

Make a back trace of the crash, and we will see :-)

> 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

cheers,
Derick

---

## #89988 — Derick Rethans — 2016-01-04T11:53:08+00:00

URL: https://externals.io/message/89950#89988 · In reply to: #89984

> On Fri, Jan 1, 2016 at 8:13 PM, Grzegorz Zdanowski
> <grzegorz129@gmail.com> wrote:
> > […]
> 
> 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