View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001288 | Xdebug | Uncategorized | public | 2016-03-25 12:27 | 2016-04-11 19:49 |
| Reporter | Arjen | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Linux | ||||
| Product Version | 2.4.0 | ||||
| Fixed in Version | 2.4.1 | ||||
| Summary | 0001288: Segfault when uncaught exception message does not contain " in " | ||||
| Description | A segfault occurs when an uncaught exceptions message does not contain the string ' in '. | ||||
| Steps To Reproduce | <?php class React_Exception extends Exception set_error_handler(function(){ throw new React_Exception('waa');}); $_SERVER['SERVER_PROTOCOL']; | ||||
| Tags | No tags attached. | ||||
| Operating System | |||||
| PHP Version | 7.0.0-7.0.4 | ||||
|
|
I had no problems with above script on a PHP 7.0.5 machine with xDebug, but my problem is reproducible with the following snippet: <code> ini_set('display_errors', 1); class myException extends \Exception { try { Effectively, adding " in " in the custom message "solves" the problem, however, notice how the returned message has been stripped, should have been: Fatal error: Uncaught my own in house custom message in /vagrant/src/test.php on line 18 is: Fatal error: Uncaught my own in /vagrant/src/test.php on line 18 When disabling display_errors no segfault occurs. No segfault on latest PHP 5.6 with latest xDebug either, but the displayed uncaught fatal error by xDebug lacks a stacktrace, with or without the " in " part of the custom exception. |
|
|
Thanks for your report! A fix for this will make it into 2.4.1. |