0001238: php-fpm7.0 crashed with SIGSEGV in xdebug_var_export()

ID	Project	Category	View Status	Date Submitted	Last Update
0001238	Xdebug	Uncategorized	public	2015-12-18 16:31	2016-01-25 21:59

Reporter	petervanderdoes	Assigned To
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	fixed
Platform	Linux	OS	Ubuntu	OS Version	15.10
Product Version	2.4.0rc3
Fixed in Version	2.4.0rc4

Summary	0001238: php-fpm7.0 crashed with SIGSEGV in xdebug_var_export()
Description	Using a WordPress site, PHP 7 crashes always, while debugging and while not debugging, at a certain point in the code. Taking this code out and checking it by itself does not produce the problem.
Steps To Reproduce	Hard to reproduce by others, it seems to specific to a certain site I have locally. Another WordPress site does not show the same problem. But the crash always occurs at the same point.
Additional Information	The code that cause the crash: function is_admin() { if ( isset( $GLOBALS['current_screen'] ) ) return $GLOBALS['current_screen']->in_admin(); elseif ( defined( 'WP_ADMIN' ) ) return WP_ADMIN; `return false;` } It crashes on return WP_ADMIN; Attached is the SegvAnalysis portion of the coredump.
Tags	No tags attached.

Operating System
PHP Version	7.0.0-7.0.4

derick 2015-12-18 16:35 administrator ~0003358	Thanks for the report and backtrace. I am pretty sure that this is 0001229 - can you try the latest source from GitHub please? cheers, Derick

aramonc 2015-12-18 16:53 reporter ~0003359 Last edited: 2015-12-18 16:54	Derick, I don't know if this helps, but I'm seeing a similar issue. Syslog reports [ 5277.283602] php-fpm7.0[29262]: segfault at 12 ip 00007f4fd4d0c082 sp 00007ffde87616e0 error 4 in xdebug.so[7f4fd4ce3000+38000] I can provide full crash report if you like. Environmnet: Ubuntu 15.10 PHP 7.0.1 - Ondrej Sury PPA XDebug 2.4.0 RC3 - Ondrej Sury PPA PHPStorm 10.0.1 App in Symfony 2.7 I'll try the mainline branch this weekend.

petervanderdoes 2015-12-18 18:27 reporter ~0003360	Cloned the repository, installed 2.4.0RC4-dev, resulted in NO crash during normal work, but crash when debugging as soon as a breakpoint is hit and you continue the program. Uploaded new backtrace.

derick 2015-12-18 18:39 administrator ~0003361	Looks like I missed one occurence of the issue. Quick fix for you to make things work while I fix it is to change any -O2 to -O0 in the Makefile after running "./configure" and before "make". Instead of just "make" you'll likely will have to run "make clean" first (but still after "./configure".

petervanderdoes 2015-12-18 19:04 reporter ~0003362	Yup that seems to solve the issue for debugging. Thanks.

petervanderdoes 2015-12-18 19:04 reporter ~0003363	And regular stuff as well, No more crashing

derick 2015-12-18 23:16 administrator ~0003364	This should now be fixed in Git's master - without the O2 ? O0 hack.

View Issue Details

Activities