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
Fixed issue #2221: Crash when other extensions run PHP code without the stack being initialised yet #938
Conversation
…he stack being initialised yet
The paths looks good (and is right). Would you have a small reproduce case with swoole perhaps? I'll see if I can turn that into a test case. |
In my system environment, I only need an empty file to reproduce: test.php: <?php
|
I don't know what your environment is though. Can you show me which extensions ( |
Turned out that this fix was also not correct. I had to do add this:
|
Closed and replaced by #939. |
|
@Yurunsoft Can you try the patch in #939? I have tried reproduce the crash with swoole on 3.3.0, but I can't manage. Perhaps I haven't set it up correctly. Sharing your |
You can also try this code: <?php
Co\run(function(){
go(function(){
usleep(1);
});
go(function(){
usleep(1);
});
}); |
my environment FROM phpswoole/swoole:5.1.1-php8.2
RUN pecl install xdebug-3.3.0 \
&& docker-php-ext-enable xdebug opcache \
&& apt-get clean \
&& php -m \
&& php --ri xdebug \
&& php --ri swoole <?php
Co\run(function () {
go (function () {
usleep(1);
echo 'Hello World#1'.PHP_EOL;
});
go (function () {
usleep(1);
echo 'Hello World#2'.PHP_EOL;
});
});
|
The fix in 5e13c7b is not complete, Swoole still has a segfault