-
Notifications
You must be signed in to change notification settings - Fork 147
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
Cannot debug with debugger in concurrent mode #617
Comments
Can you add an output of the current code in this file : var_dump(getenv('XDEBUG_CONFIG')); |
@mikaelrandy see follow the complete output $ ./vendor/bin/atoum -xc "idekey=DEBUGMETHAT" -mcn 1 -d tests/units
> atoum path: /Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/./vendor/bin/atoum
> atoum version: dev-master
> PHP path: /usr/local/Cellar/php70/7.0.7/bin/php
> PHP version:
=> PHP 7.0.7 (cli) (built: May 27 2016 11:13:44) ( NTS )
=> Copyright (c) 1997-2016 The PHP Group
=> Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
=> with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
=> with Xdebug v2.4.0, Copyright (c) 2002-2016, by Derick Rethans
> Workshop\tests\units\Countdown...
[..__________________________________________________________][0/2]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S.__________________________________________________________][1/2]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S__________________________________________________________][2/2]
=> Test duration: 0.13 second.
=> Memory usage: 0.00 Mb.
> Workshop\tests\units\Moment...
[....________________________________________________________][0/4]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S...________________________________________________________][1/4]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S..________________________________________________________][2/4]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S.________________________________________________________][3/4]/Users/ashgenesis/dev/tmp/workshop-tdd/vendor/atoum/atoum/classes/test/engines/concurrent.php:188:
bool(false)
S________________________________________________________][4/4]
=> Test duration: 0.05 second.
=> Memory usage: 0.00 Mb.
> Total tests duration: 0.18 second.
> Total tests memory usage: 0.00 Mb.
> Code coverage value: 88.46%
=> Class Workshop\Countdown: 88.89%
==> Workshop\Countdown::computeNumberOfCheckedBox(): 66.67%
==> Workshop\Countdown::draw(): 85.71%
=> Class Workshop\Moment: 87.50%
==> Workshop\Moment::getDatetime(): 0.00%
> Running duration: 0.74 second.
Success (2 tests, 6/6 methods, 0 void method, 0 skipped method, 66 assertions)!
> There is 1 output:
=> In Workshop\tests\units\Moment::testNewInstance():
/Users/ashgenesis/dev/tmp/workshop-tdd/tests/units/src/Moment.php:9:
string(18) "idekey=DEBUGMETHAT" I have added the var_dump ligne 188 as asked and added also in test class. (cf: output) As see apparently, the constant is correctly recognized in test class but not in atoum process. (false) |
I had similar issue with previous releases; but this seems to be fixed now; I'm able to set breakpoints even with default mode. |
It works well when I use the inline engine and I can debug my code but If I use the concurrent engine I cannot break on breakpoint.
And, if I remove the first constant, I have a break on nowhere (no file displayed) and all existants breakpoint doesn't work. The script continue to be executed. I can dig into process with
step into
andstep out
command of debugger but no breakpoint react (breakpoint are in tests classes)./vendor/bin/atoum -xc "idekey=DEBUGMETHAT" -mcn 1 -d tests/units
Here my xdebug configuration
I use vdebug (joonty/vdebug.git) and vim to debug
atoum --version
=>67104f2d0f0bdea40343428b8ba6f289a0d948ae
The text was updated successfully, but these errors were encountered: