I had been running Centos7 with PHP 7.3, Apache 2.4, php-fpm, and NuSphere PhpED 19.1 Professional for Windows (Build 19116) and all was working fine.

I just upgraded to PHP 7.4.1 (using remi's repository) and NuSphere PhpED 19.2 Professional for Windows (Build 19210) but now the wizard shows the following error when Checking debugger in HTTP (web server) mode step:



The Nusphere documentation states PHP7.4 is supported and that glibc must be equal to or greater than 2.3, however, my glibc version is 2.17 so why is this an issue? Additional details as follows:

Thank you!

php.ini is set up as follows:



Specific details from the wizard are as follows:


Step 2...


According to http://www.nusphere.com/products/debugging_php.htm



phpinfo() provides the following:



The only reference to glibc under phpinfo is:



glibc information is also found using the following:

- dbg-wizard script should and will be updated (ETA - in 2h)
- http://www.nusphere.com/products/debugging_php.htm -- should and will be updated (ETA - in 2h)
- Error: (-125) failed to evaluate "$arg1", error: -- I'm not sure what happened with it -- Please check server logs. There should be a reason for 503.

PS
Zend OPcache
^^^^^^^^^^
I'd highly recommend you to remove this guy from your development server

Wow, That is the quickest turnaround I've ever experienced. Thanks!

I will check into the "arg1" error and post my findings

And yep, it has been on my list to remove Zend OPcache and will make it happen before the New Year.

Thanks again, Michael

- Original issues with dbg-wizard. Fixed as you promised. Thanks!

- Zend OPcache. Removed as I promised.

- Error: (-125) failed to evaluate "$arg1", error

journalctl shows the following. Is this on my end or yours? PS. I don't know what those hex values mean but if I shouldn't be posting them public, please delete/change them from this post.

- check TS requirements of your php. If it is non-thread-safe, you have to use non-thread-safe debugger module
- check sha2 or md5 sum of the share library to make sure it wasn't corrupted when you transferred it to your server. Just for instance it's known that WinSCP corrupts binary files.
- if nothing helps, try to configure php to produce coredump to get full callstack. Then submit it in your ticket

PS under "share library" I mean shared object, .so file, the debugger binary that you copied to the server. It's shouldn't be an issue if you copy .tar.gz archive then unpack it on the server with verification. But if you unpack it locally and copy only .so file, it may be corrupted. It was the root cause in dozen cases.

I documented the following, but at the very end everything started working for unknown reasons. Just in case it helps you or others, I am still posting my results. Also, just for curiosity's sake (or just in case it happens again), any suggestions for probable cause would be appreciated. Thanks

I think I am using the correct non-thread safety debugger. Please see below.
I rarely use WinSCP. See below how I uploaded content to the server and if necessary please elaborate on what you mean by checking the share library.
See the steps I took regarding a coredump, however, nothing was saved in any of the \tmp directories.

----

I un-installed all instances of PhpED on my Windows PC and reinstalled full installation NuSphere-phped-19.2-x64.exe.

I copied the debugger to the server:


lscpu reports: Architecture: x86_64 and CPU op-mode(s): 32-bit, 64-bit

I replaced the debugger with the new version:

I changed php.ini to the following as it worked this way previously:


I restarted the server. Note that I am using php-fpm which previously worked fine.


I used the wizard to configure:



POP-UP 1: New debug session with //api.myserver.net:443/dbg-sample.php has started. But IDE could not find the project for the web debugging. Breakpoints and other features may fail to work.
POP-UP 2: Error: Debug session unexpectedly terminated.

Clicking api.myserver.net/dbg-sample.php displays:


journalctl logs: Dec 31 14:36:27 myserver.net kernel: traps: php-fpm[5328] general protection ip:7f48549ddab6 sp:7fff8e0423e0 error:0 in dbg-php-7.4.so[7f48549c4000+31000]


Steps to configure coredump:


I repeated the wizard and journalctl reported the same error . I expected some content in the /tmp directory but there was none. I even changed the folders to 0777 but still none.



For some odd reason, the PhpED project I was working with lost all its settings. I reentered them, but PhpED said the ssh file couldn't be found. I rebooted PhpED, and now all is good

I returned the php-fpm config files to their original state and rebooted the server. I still need to figure out how to reverse the following and will figure it out, but would still appreciate any help you can provide.

In case if problem is still there, do not disable coredumps for a while. If you get anything like "503" or "Debug session unexpectedly terminated", check core directory grab callstack if core is creted. Try to reproduce too.

As of "New debug session with //api.myserver.net:443/dbg-sample.php has started But IDE could not find the project", it's weird. I'll try to reproduce it in our premises.

Thanks again dmitri, If the problem resurfaces, I will post the results, else looks like I am good to go. Happy New Year!

Problem was reproduced and a workaround found. Dbg-9.2.8 is available as a component of PhpED 19212

Good timing. Problem just came back today and came back to this post for reference and saw that you got it fixed. All working!

Side topic. For these updates, do I need to reinstall PhpED or just the debugger?

Also, sometimes it seems to install in C:\Program Files\NuSphere and other times in C:\Program Files (x86)\NuSphere. Which one should it be located in?

Thanks

1 -- yes you'd better install
2 -- (x86) is for 32bit software on 64bit OS. You don't have a reason to do that, right?