0000830: Crash when evaluating variables from remote Eclipse IDE

ID	Project	Category	View Status	Date Submitted	Last Update
0000830	Xdebug	Uncategorized	public	2012-05-11 00:29	2012-05-28 12:04

Reporter	nlaplante	Assigned To
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	fixed
Platform	PHP 5.4.0 Apache 2.2.22	OS	Gentoo Linux amd64	OS Version	3.2.12
Product Version	2.2.0
Target Version	2.2.1	Fixed in Version	2.2.1

Summary	0000830: Crash when evaluating variables from remote Eclipse IDE
Description	I experience an XDebug crash when trying to debug variables (either by hovering it or opening the variables pane). First, Eclipse throws this error message: "Unexpected termination of script, debugging ended." The Apache error_log contains this: "[error] child died with signal 11"
Steps To Reproduce	Define breakpoint in Eclipse Start debug session in Eclipse When at breakpoint, either open variables pane or hover a variable in the editor
Additional Information	I tried using watch expressions. I noticed that if I put the name of variables I expect are strings, it works fine. But if I add an expression to evaluate an object , xdebug crashes with the error specified in the description.
Tags	No tags attached.

Operating System
PHP Version	5.4.0

derick 2012-05-13 21:51 administrator ~0002149	Hi, In order to reproduce and fix this, I'd need the following information: A short and self-contained script that reproduces the issue while debugging A debugging log, which you can make with setting xdebug.remote_log=/tmp/xdebug.log cheers, Derick

nlaplante 2012-05-14 21:55 reporter ~0002150	I can't reproduce the problem outside of my Symfony 2 environment. Maybe it has to do with the autoloading mechanism? I attach my xdebug.log file.

derick 2012-05-15 09:43 administrator ~0002153	It's probably not autoloading, but something to do with (static) properties instead. Could you perhaps try making a backtrace for me? (See: https://bugs.php.net/bugs-generating-backtrace.php)

nlaplante 2012-05-15 22:02 reporter ~0002154	I uploaded the backtrace. Let me know if you need anything

derick 2012-05-15 22:07 administrator ~0002155	Awesome, sorry to be a pain, but could you please also run: p *struc bt full

nlaplante 2012-05-15 22:09 reporter ~0002156	Here you are!

nlaplante 2012-05-15 22:10 reporter ~0002157	Don't use -bt.2.log, I forgot to run "bt full". Use -bt.3.log instead.

derick 2012-05-16 21:07 administrator ~0002162	Hi, I've tried this with just Monolog, which is where the crash seems to happen. However, I have not made any success. It it possible for you to create a full setup for me, in for example a VM that I could debug?

nlaplante 2012-05-17 00:00 reporter ~0002163	Yes. I opened up my app at http://nlaplante.dyndns.org:8080/app_dev.php XDebug is enabled, you can go and try it. Let me know when you're finished,

derick 2012-05-17 07:33 administrator ~0002167	Hi, Just having access to the website is not going to help me; I'd need shell access to probe the innards of Xdebug as well! cheers, Derick

nlaplante 2012-05-17 11:19 reporter ~0002174	Derick, please contact me at nicolas.laplante@gmail.com. I'll give you ssh credentials to log into the system.

nlaplante 2012-05-17 21:10 reporter ~0002179	I think it would be a better idea for you to checkout a copy of my project instead. Here's the svn url: http://svn.nlaplante.com/profolio/branches/xdebug Email me for credentials at the address in the previous comment. Thanks!

derick 2012-05-28 08:26 administrator ~0002200	I think I've just pushed a fix to github for this issue. Could you please try it?

nlaplante 2012-05-28 11:34 reporter ~0002207	I just tested your fix and it seems to work fine. XDebug doesn't crash on variable inspection anymore, and I can dig into objects normally!

View Issue Details

Activities