View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002271 | Xdebug | Uncategorized | public | 2024-06-11 21:34 | 2024-07-18 13:36 |
Reporter | jfox97 | Assigned To | derick | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | unable to reproduce | ||
Platform | Docker - arm64v8/ubuntu | OS | macOS | OS Version | Ventura 13.6.7 |
Product Version | 3.3.2 | ||||
Summary | 0002271: Segmentation fault whenever php8.1-xdebug extension is enabled | ||||
Description | We're getting segmentation faults from php-fpm whenever the php8.1-xdebug extension is enabled. This issue occurs consistently within our docker container built on the arm64v8/ubuntu base image. The docker engine is running on a macOS Ventura host. We get the following stack trace from the core dump: Reading symbols from /usr/sbin/php-fpm8.1... warning: Source file is more recent than executable. (gdb) bt | ||||
Additional Information | The issue does not occur on php 8.3 with the php8.3-xdebug extension. We have not tested on php 8.2. I have the full core dump file, but am unable to attach it to the bug report due to its size. | ||||
Tags | No tags attached. | ||||
Operating System | |||||
PHP Version | 8.1.10-8.1.19 | ||||
|
How can I reproduce this? Your ticket does not mention anything about this. |
|
Can you provide the requested feedback? |
|
It reproduces consistently in our environment, but we don't know specifically what about our environment is causing this for you to be able to reproduce it. The lowest level of the core dump we have symbols for is that xdebug_execute_internal method. Sorry, I know that's not helpful. I still have the core dump I can send you if there's a way to send you files larger than 5 MB. With the right debugging symbols, that'll likely give the context needed to be able to reproduce. |
|
I should add, it reproduces consistently in our environment whenever xdebug is enabled, a break point is set, and we execute a specific operation in our app. We don't know what's unique about the operation that seems to be triggering this. |
|
I do not yet have a way on how to reproduce this problem. There are currently several reported crash bugs where more than one person added information, but often with a different cause. This makes researching this challenging, especially because I still do not have a reproducible case. I am going to close this ticket (and the others), and will only accept issues related to crashes when there is a full reproducible case — the exact steps on how I could potentially try to have the same issue. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-06-11 21:34 | jfox97 | New Issue | |
2024-06-17 23:32 | derick | Assigned To | => derick |
2024-06-17 23:32 | derick | Status | new => feedback |
2024-06-17 23:32 | derick | Note Added: 0006979 | |
2024-07-10 16:04 | derick | Note Added: 0006988 | |
2024-07-10 21:56 | jfox97 | Note Added: 0006992 | |
2024-07-10 21:56 | jfox97 | Status | feedback => assigned |
2024-07-10 21:58 | jfox97 | Note Added: 0006993 | |
2024-07-18 13:36 | derick | Status | assigned => resolved |
2024-07-18 13:36 | derick | Resolution | open => unable to reproduce |
2024-07-18 13:36 | derick | Note Added: 0007013 |