View Issue Details

IDProjectCategoryView StatusLast Update
0002016XdebugUncategorizedpublic2021-09-16 11:32
ReporterJeremyDunn Assigned To 
PriorityhighSeverityblockReproducibilityalways
Status newResolutionopen 
PlatformWindowsOSWindowsOS VersionWin10 Pro 21H1
Product Version3.1.0beta2 
Target Version3.1dev 
Summary0002016: apache gives no output with xdebug 3.1.0b2 installed
Descriptionreplaced 3.0.4 which works fine, with 3.1b2
running apache 2.4.47 x64 built by apachelounge

open a simple PHP page that has only phpinfo();
with xdebug 3.1.0b2 installed, page gives *NO OUTPUT*. Works fine with 3.0.4
Steps To Reproduce1. download 3.1.0b2 8.0 TS x64
2. install to php/ext folder
3. change php.ini extension name
4. restart apache - log shows it starts ok
5. open a simple script which contains only phpinfo();

previously shows PHP 8.0.8 with xdebug 3.0.4
now shows *nothing* - no output whatsoever

6. from command line : php -r "phpinfo();" WORKS and shows xdebug 3.1.0b2 is loaded.

Looks like the problem may be in apache/xdebug interaction
I'm on apache 2.4.47 build by apachelounge - works fine for xdebug 3.0.4

upgraded to httpd 2.4.48 with the SAME behavior: 3.0.4 works fine; 3.1.0b2 produces no output
Additional Informationthere is nothing unusual in apache error log; nothing in xdebug.log; nothing in PHP error log

C:\Users\Jeremy>php -v
PHP 8.0.8 (cli) (built: Jun 29 2021 16:02:52) ( ZTS Visual C++ 2019 x64 )
Copyright (c) The PHP Group
Zend Engine v4.0.8, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.8, Copyright (c), by Zend Technologies
    with Xdebug v3.1.0beta2, Copyright (c) 2002-2021, by Derick Rethans

(NOTE: PHP version selector in Mantis only goes to 8.0.4 - I'm running 8.0.8)

PHP.ini:
======
;zend_extension=php_xdebug-3.0.4-8.0-vs16-x86_64.dll
zend_extension=php_xdebug-3.1.0beta2-8.0-vs16-x86_64.dll

[xdebug]
xdebug.log="<PATH-REMOVED>\xdebug.log"
xdebug.mode=debug
xdebug.client_host=localhost
xdebug.client_port=9000
xdebug.idekey="netbeans-xdebug"
xdebug.output_dir="<PATH-REMOVED>"
xdebug.var_display_max_depth=20
xdebug.var_display_max_children=-1
xdebug.var_display_max_data=-1
TagsNo tags attached.
Operating SystemWindows 10 Pro 21H1
PHP Version8.0.0-8.0.4

Activities

derick

2021-09-16 08:48

administrator   ~0006007

I'm not quite sure how to dive into this. Is there Anything in your PHP or Apache error logs perhaps? A note of a crash, or some other error?

JeremyDunn

2021-09-16 09:42

reporter   ~0006011

xdebug log after restarting Apache with 3.1.0b2 installed:

[23900] Log opened at 2021-09-16 09:28:00.704547
[23900] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION'
[23900] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating

has something changed in the config required between 3.0.4 and 3.1.0b2 ? all my php.ini entries related to xdebug are in the original problem report
=====
there is nothing in the apache error log; but it looks like xdebug / apache httpd crashed. this is from the Windows Event log:

Faulting application name: httpd.exe, version: 2.4.48.0, time stamp: 0x612616a0
Faulting module name: php_xdebug-3.1.0beta2-8.0-vs16-x86_64.dll, version: 3.1.0.1, time stamp: 0x6137725c
Exception code: 0xc0000005
Fault offset: 0x000000000000c7f0
Faulting process id: 0x1808
Faulting application start time: 0x01d7aadd0c7915cd
Faulting application path: C:\Program Files\Apache2.4.48\bin\httpd.exe
Faulting module path: C:\Program Files\php8\ext\php_xdebug-3.1.0beta2-8.0-vs16-x86_64.dll
Report Id: 8d1802bc-1629-4e42-b042-900328c67ae7
Faulting package full name:
Faulting package-relative application ID:

=====
I installed windows procdump64 and it generated TWO .dmp files when apache crashed, both of which are 4mb. Are these of any value? And/or would it be helpful for me to follow the instructions here (https://bugs.php.net/bugs-generating-backtrace-win32.php) to run DebugDiag? I have no experience with this but am willing to try. Please advise.

JeremyDunn

2021-09-16 11:32

reporter   ~0006018

attached is the DebugDiag analysis for the crash dumps mentioned in previous comment

one note: I'm running PHP 8.0.8 but downloaded debug-pack 8.0.10 because it was handy. Please let me know if this causes a problem and I'll do it again...

Issue History

Date Modified Username Field Change
2021-09-14 18:35 JeremyDunn New Issue
2021-09-16 08:48 derick Status new => feedback
2021-09-16 08:48 derick Target Version => 3.1dev
2021-09-16 08:48 derick Note Added: 0006007
2021-09-16 09:42 JeremyDunn Note Added: 0006011
2021-09-16 09:42 JeremyDunn Status feedback => new
2021-09-16 11:32 JeremyDunn Note Added: 0006018
2021-09-16 11:32 JeremyDunn File Added: MultipleDumps_CrashHangAnalysis.mht