Please provide the exact steps as to how I can reproduce this.

Presume I know nothing beyond normal PHP.

Hi Derick.

I'd have to write a whole public project to reproduce this error with generic code.
It'll take some time...

That's okay. I'd love for you to not have to do this, but I don't even know where to start building a Laminas project.

I have released Xdebug 3.3.1, which could have fixed this issue. Can you please try it?

Hi Derick,

I can confirm that the issue is still present in version 3.3.1, although I'm not sure it is connected with reflection.

Can you provide a (short) reproducible case then? I wouldn't know where to start here. Presume I know nothing about Laminas. Or perhaps at least provide a backtrace and xdebug log (https://xdebug.org/reporting-bugs#step-debugger) to begin? If I can't reproduce it, I also likely can't fix it.

I would gladly provide the xdebug logs, but is there a way to send it over a private channel? I wouldn't want to make the specifics of our company software public domain.

I also just found out that the problem occurs also when running a script through a web server's fcgi proxy to PHP-FPM, although instead of the "Segmentation fault" I get the following errors in the web server error logs along with a 503 Service Unavailable response.

Nginx:

2024/01/05 12:41:58 [error] 47#47: *10 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 223.223.0.1, server: $host, request: "GET /some-resource/1?XDEBUG_SESSION=asd HTTP/1.1", upstream: "fastcgi://223.223.0.37:9090", host: "127.0.0.1:19492"

Apache:

[Fri Jan 05 12:38:48.373555 2024] [proxy_fcgi:error] [pid 34:tid 140142342183736] [client 223.223.0.1:52312] AH01067: Failed to read FastCGI header
[Fri Jan 05 12:38:48.373602 2024] [proxy_fcgi:error] [pid 34:tid 140142342183736] (104)Connection reset by peer: [client 223.223.0.1:52312] AH01075: Error dispatching request to :18492

I think this might be the same issue as 0002229.

I can confirm that updating to PHP-8.2 solves this issue.

I have released Xdebug 3.3.1, which could have fixed this issue. Can you please try it?

Can you provide the requested feedback please?

Hi @derick,

Sorry for the late reply.

I moved jobs and, "unfortunately", I can't test this anymore.
This also means I can't replicate the issue anymore, it's working for my current applications.

Unless anyone else can contribute, I'm fine with closing this issue.

Hi,

thanks for getting back to me.

If you encounter it again, or something else, please feel free to file another report. I promise to be speedier about it!

cheers,
Derick