View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001636 | Xdebug | Uncategorized | public | 2019-02-21 10:14 | 2019-02-23 12:53 |
Reporter | chrisminett | Assigned To | derick | ||
Priority | normal | Severity | crash | Reproducibility | sometimes |
Status | resolved | Resolution | no change required | ||
OS | macOS | OS Version | 10.14.3 | ||
Product Version | 2.7.0RC2 | ||||
Summary | 0001636: Segmentation fault for phpunit on php 7.3.2 | ||||
Description | Sorry this is going to be an incomplete report. I'm getting a seg fault when attempting to run PHPUnit using PHP 7.3.2 with Xdebug 2.7.0RC2 however it only happens with our main project, and all our smaller packages appear to run without issue. I've followed the bug reporting issues, and installed gdb, including the code-signing steps, only to find it's not compatible with Mojave. Also, Valgrind isn't compatible with Mojave, so I'm stuck to include any useful information. Please let me know if there's any way I can dig further into this. Here's the output with the two exports. There are two variants of errors:
| ||||
Tags | No tags attached. | ||||
Operating System | macOS Mojave 10.14.3 | ||||
PHP Version | 7.3.2-7.3.4 | ||||
|
OK, so this might actually be my mistake. I was looking to test the fix for 0001625 which was affecting us, but actually the issue I've posted here continues without Xdebug loaded. :( Please close! |
|
Hi, that's all right — please do file a bug at https://bugs.php.net though, and if you have already done so, would you please mind adding a link to the php.net issue here? cheers, |
|
Hi Derick, Thanks for the update. I've managed to find the culprit by trial and error running different unit tests. It's down to ext-mailparse, which is not yet compatible with php73 (but has unreleased commits which suggest support is coming http://git.php.net/?p=pecl/mail/mailparse.git ). My php install comes from MacPorts, which has added a php73-mailparse port using the 2016 release of mailparse 3.0.2. I've reported to MacPorts that this is not yet compatible: https://trac.macports.org/ticket/58111 Thanks, |
|
That's for letting me know! I'm closing this, at it turned out to be a bug in the mailparse extension. |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-02-21 10:14 | chrisminett | New Issue | |
2019-02-21 11:58 | chrisminett | Note Added: 0004916 | |
2019-02-21 22:08 | derick | Assigned To | => derick |
2019-02-21 22:08 | derick | Status | new => feedback |
2019-02-21 22:08 | derick | Note Added: 0004920 | |
2019-02-22 10:13 | chrisminett | Note Added: 0004922 | |
2019-02-22 10:13 | chrisminett | Status | feedback => assigned |
2019-02-23 12:53 | derick | Status | assigned => resolved |
2019-02-23 12:53 | derick | Resolution | open => no change required |
2019-02-23 12:53 | derick | Note Added: 0004923 | |
2020-03-12 16:35 | derick | Category | Usage problems (Wrong Results) => Variable Display |
2020-03-12 16:38 | derick | Category | Variable Display => Uncategorized |