-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Phalcon\Config->get() is crashing Phalcon: "invalid opcode in phalcon.so". #1739
Comments
Hm. Compiling it from ext/ fixed the crash. I may have used a wrong php-config when I compiled it the first time. Actually, how can I compile Phalcon and indicate which of the two available php-config utils to use? |
./configure --with-php-config=/path/to/php-config
This means that gcc generated something very wrong that is not supported by your processor (I noticed several times that |
:-) no, thank you. doesn't look it needs debugging. I just think that the wrong php-config got in the way. My question was - how do I use automatic build/install and still be able to point to the right php-config? |
I think you will have to edit ./build/install script: #Perform the compilation
phpize && ./configure --enable-phalcon && make && make install && echo -e "\nThanks for compiling Phalcon!\nBuild succeed: Please restart your web server to complete the installation" Replace with #Perform the compilation
/path/to/proper/phpize && ./configure --with-php-config=/path/to/php-config --enable-phalcon && make && make install && echo -e "\nThanks for compiling Phalcon!\nBuild succeed: Please restart your web server to complete the installation" |
ok, something is definitely wrong. I did fix ./build/install script according to your instructions, but phalcon.so is crashing again on the same line. Compiling it from ext/ results in: Fatal error: Call to undefined method Phalcon\Mvc\View::isDisabled() Can we investigate it? Thanks! |
let me do a bit of investigation before we return to this. |
Here's the situation with latest 1.3.0.
/var/web/php/bin/phpize
./configure CFLAGS="-O0 -g3" --with-php-config=/var/web/php/bin/php-config
make -j4
sudo make install then #1714 is back. Editing ext/di.c and commenting out: if (!nusphere_dbg_present) {
/*phalcon_di_object_handlers.get_properties = phalcon_di_get_properties;*/
} and recompiling fixes everything. So, two questions:
Thanks! |
As for 1 — this is probably a bug ig gcc — I suspect it uses AVX instructions though they are not supported by your CPU. Could you please:
|
I'm gonna get to this issue a bit later. It's still on my radar. |
Not sure what was going on earlier. I've just compiled latest 1.3.0 and all is well. I still suspect that something is not right on systems where there are two php-config files and the one that's picked up by the script isn't the one that belongs to currently used PHP instance. |
thanks @temuri416 ! compiling from ext/ fixed same problem for me on php 5.5.10 and phalcon 1.3.1. |
The set-up:
Very early in the exec cycle of my app there's this code:
Executing
$config->get()
crashes php-fpm with the following message in kern.log:Please help :-)
Thanks!
The text was updated successfully, but these errors were encountered: