You can see a Bugreport at PhpStorm Team from me
https://intellij-support.jetbrains.com/hc/en-us/requests/4394303

The Jetbrain Supporter writes
"Thanks for the update. I'm also not able to generate a valid profiler snapshot using XDebug 3.1.5. Looks like an XDebug issue to me.
Let me know if there's anything else I can assist you with."

Hi,

thanks for this report. It looks like the GZIP file has all binary \0a characters replaced with \0d \0a, (ie, \n to \r\n, or Linux line endings to Windows line endings). I think I have a fix for that in https://github.com/xdebug/xdebug/pull/864, but I can not test this, as I don't have access to Windows.

I can't see the jetbrains report, it says the URL does not exist, but there should soon be a DLL with a fix for you to try at https://github.com/xdebug/xdebug/actions/runs/3290947479#artifacts

cheers,
Derick

Hi,
sorry i can not compile the Source-Code and i think Xdebug 3.2 i can not run this with PHP 7.4.29.
At this time i can not change to PHP >= 8.
Best regards
Hajo

Hi,

Sorry it took some time, but I now have Windows DLLs for you for Xdebug 3.1.x, which includes PHP 7.4 support:
https://github.com/xdebug/xdebug/actions/runs/3376665362#artifacts

If you can confirm that this works, I will make a 3.1.6 release ASAP.

cheers,
Derick

Hi,
i have download the "php_xdebug-3.1.6-dev-7.4-vc15-x86_64.dll" and test it with profile and trace output.
Profile output-File is OK, i can use it.
Trace output-File show a CRC-Error.

cheers,
Hajo

CRC-Error.JPG (54,726 bytes)   

CRC-Error.JPG (54,726 bytes)   

Can you please attach the trace file? I don't know where a CRC failure would come from, as the file format doesn't really have a CRC checksum.

Hi,
my trace output files are to large to load up here.
I have build a small php script with mini code to generate a small trace output File.

cheers,
Hajo

Thanks for that file, it seems to be the same problem with trace files, then the one I fixed for compressed files. I thought my fix had fixed both, but I must have missed something.

I think I've fixed these as well now. There is a new DLL at https://github.com/xdebug/xdebug/actions/runs/3411352967#artifacts — would you please be able to check that? If it works, I'll make a 3.1.6 release.

Hi,
this Dll Version (php_xdebug-3.1.6-dev-7.4-vc15-x86_64.dll) produce a good trace-File.

cheers,
Hajo

Excellent. I'll merge it then and release 3.1.6 tomorrow.

Hello Derick,
this day i must work under PHP 8.1 and i use the "php_xdebug-3.2.0RC1-8.1-vs16-x86_64.dll" under Windows!
It seems to me there is the same Problem/Bug under Windows. In Attachment you find a trace and a profile File
from a little Test .

I have see the Release xdebug 3.1.6 is set, so i use the 3.1.6 as review.

cheers Hajo

The 3.2.0RC1 release was made before the fix, so it will have the same problem as 3.1.5. The Xdebug 3.1.6 release for PHP 8.1 (https://xdebug.org/files/php_xdebug-3.1.6-8.1-vs16-x86_64.dll) should work though. In general, I wouldn't recommend running Release Candidates (RCs) unless you're just testing it out. I will be making Xdebug 3.2.0RC2 shortly, and that should also contain the fix.