Crash without feedback

[silas2]

I'm running one of those really dense zend-based frameworks with masses of recursion (Magento), and I'm getting a problem with reading/writing the session, before I deal with that I'm trying to find some feedback on where the issue is happening.

I've got everything ( i know of ) switched on, 

error_reporting(E_ALL);
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);

+ I'm using PHPStorm with Xdebug and I've got Php Exception breakpoint set, I'm watching the Phpstorm Output/Console/Terminal (don't quite know the difference) +var/log/Exception.log, but....It just hangs without telling me which line.

Is this someting I've got to take on the chin with Php (I'm a relative newbie)? Or is there some way else?

Debian/Php 7.3

[gw1500se]

Did you check the httpd log?

[silas2]

Is that the same as  /var/log/apache2/error.log in Debian? 

[gw1500se]

Yes. There is also access.log but that probably won't help much.

[silas2]

Mmmm.....I'm getting an apache segmentation fault, that's pretty bad isn't it? I mean mega difficult to diagnose.

[gw1500se]

Not necessarily. There should be a segmentation fault number (e.g. segmentation fault (11)).

[silas2]

Got it in one. Yes 11.

 

[silas2]

I might add that I have other Magento installations on the same PC and they seem to be working fine so I'm guessing the Phpstorm+xdebug setup may not be the culprit...but then again..

[gw1500se]

Fault 11 is memory. You probably need to change memory_limit in your php.ini. I think it is 128M by default so you might try 256M.

[silas2]

I've upped it to 256 and I'm still getting the problem. This is where I am diagnostically:

If I disable xdebug it runs fine.

If I enable xdebug I still get the fault 11 even with the 256M - is it going into some sort of recursion?

When I step thru code I get the spooky affect of if I step in a procedure it behaves ok, if I step over the same procedure it crashes.

Other Magento apps on the same box, same xdebug setup are ok.

Do you think (desperate measure? ), its something like file corruption in the app and just re-install it? 

 

[gw1500se]

Its possible but you might try going to 512K on your memory first. Magento is a separate thing so it would not effect PHP max memory. It would only effect total memory and I assume you have at least 8G. How big is your swap? Although I doubt that would cause a memory fault.

[silas2]

Nope...I just set it to memory_limit = -1 - that means unlimited doesn't it? I've got 16GB so should cope with anything I guess.

(NB I am restarting Apache each time)

 

 

[gw1500se]

Assuming your swap space is sufficient, I guess you are stuck with trying to reinstall PHP and maybe Apache.

[silas2]

That's what I was saying about the other Magento Installs on the same PC, they're working OK so I assume there's nothing wrong with PHP/xdebug/apache, but maybe there's corruption in the project files for this one project where I have the problem?