|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #78476 Segfault when running Monolog test suite on 7.4snapshot
Submitted: 2019-08-30 13:50 UTC Modified: 2019-11-07 11:05 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: Assigned: nikic (profile)
Status: Closed Package: Reproducible crash
PHP Version: 7.4Git-2019-08-30 (snap) OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
44 + 48 = ?
Subscribe to this entry?

 [2019-08-30 13:50 UTC]
See Travis job output. That's all the info I have sorry no time to dig further at the moment.

Test script:
composer create-project monolog/monolog
cd monolog

Expected result:
No segfault :)

Actual result:
Segfault :(


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-08-30 13:57 UTC]
Can't reproduce with current 7.4 HEAD.
 [2019-09-01 13:28 UTC]
-Status: Open +Status: Verified
 [2019-09-01 13:28 UTC]
Can reproduce with opcache ... didn't know that's enabled on Travis.
 [2019-09-02 07:57 UTC]
Heh, this is a stack overflow caused by infinite recursion in the error handler for a "Trying to access array offset on value of type null" notice.

The original notice is triggered in and the infinite recursion occurs in

Not sure where the opcache-specific bit in this is.
 [2019-09-02 08:10 UTC]
@seld: The problematic error handler is set up here:

So while there is presumably also an opcache bug here that causes the notice in the first place, this code should probably also be fixed to make sure that any notice thrown in the testsuite does not automatically turn into a stack overflow segfault.
 [2019-09-05 13:29 UTC]
Ok thanks for the find. I fixed it in which fixes the build. 

It seems to pass without notice either so I am not sure how this is possible. If opcache caused the notice which then crashed with the segfault the notice should still be there. If opcache had only an issue with the error handler then it should show a notice now?
 [2019-09-12 10:08 UTC]
@seld: If I patch to throw an exception if $responses is null, then I do get that exception. So the notice should also be thrown -- there's probably still an error handler around that suppresses it.

That said, I get the null value there both with and without opcache, so I'm not sure what the role of opcache was here originally...
 [2019-11-07 11:05 UTC]
-Status: Verified +Status: Closed -Assigned To: +Assigned To: nikic
 [2019-11-07 11:05 UTC]
Closing this as the original issue was resolved...
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Thu Aug 13 08:01:24 2020 UTC