Opened 6 years ago

Closed 2 years ago

#46957 closed defect (worksforme)

php55-xdebug @2.3.0_0 - Segmentation fault 11

Reported by: anthony.clarke@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port: php-xdebug

Description

Using either the prepackaged port or building from source results in a "Segmentation fault: 11" error when executing php55 (or "php" if php55 is selected as current) either with or without a script when php55-xdebug @2.3.0_0 is installed.

In order to test, all php packages were removed cleaned and then reinstalled one by one, with php55-xdebug last. The segfault only occurred on this last step.

Finally all of php and additional modules were uninstalled and port cleaned. Just 'php55' was installed and tested as okay, followed by installing 'php55-xdebug' which immediately resulted in a segfault on executing 'php55'

The same procedure was then performed on php56 with php56-xdebug @2.3.0_0 - all tests okay.

It seems php55-xdebug @2.3.0_0 is currently broken.

Other information: Yosemite 10.10.2 - Xcode Version 6.1.1 (6A2008a)

Change History (4)

comment:1 Changed 6 years ago by ryandesign (Ryan Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Port: php-xdebug added

I updated the port to 2.3.1 in r133304. Did that help? If not, you should probably report the problem to the developer of xdebug.

comment:2 Changed 6 years ago by anthony.clarke@…

Many thanks for the rapid update!

No joy I'm afraid. I'll dig into the code and see if I can see anything obvious. I'll also try everything on a clean machine - you never know. I'll raise an issue on xdebug.org once I have gone as far as I can go.

In the mean time, php56-xdebug is working @2.3.1_0 and everything else appears stable so I'll move my dev team to that version.

comment:3 Changed 6 years ago by anthony.clarke@…

Having kept at this for 24 hours I find I can cause the problem on PHP 5.6.x, too. I removed all ports, macports, xcode and started again - this time with all code build from source not packages. Everything is now working.

On a second machine which is in a similar state I found that if I performed:

sudo port -v selfupdate
sudo port upgrade outdated

all was okay, but as soon as I did:

sudo port uninstall inactive

php would segfault with xdebug installed.

It now looks like a dependency is getting removed as inactive when it's actually in use.

This is where I have to stop looking. Otherwise I think this thread should be closed. Thanks for the help.

Last edited 2 years ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:4 in reply to:  3 Changed 2 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed

Replying to anthony.clarke@…:

all was okay, but as soon as I did:

sudo port uninstall inactive

php would segfault with xdebug installed.

It now looks like a dependency is getting removed as inactive when it's actually in use.

That's not possible. When a port is deactivated, all of its files are deleted from disk; all that remains is a tar.bz2 archive of those files. (If the port is reactivated, that archive is extracted.) So, if xdebug was working prior to uninstalling inactive ports, it's impossible that uninstalling inactive ports would break it. Perhaps you misremembered which commands you ran.

In any case, if you or anyone is still experiencing a crash, please file a bug report with the developer of xdebug. Remember to attach a macOS crash log file.

Note: See TracTickets for help on using tickets.