Steps to reproduce:

Install PHP 7.2 beta with MSVC15 for Win, you will lose the functionality of most of the extensions.

Open the website:

Provide your phpinfo() output

See this line:

Get this:

When I load the downloads page
https://xdebug.org/download.php

it sits there loading until Google Chome says "Awww Snap!"

This even occurs with the archived snapshot of the page :-(
https://web.archive.org/web/20190309133508/https://xdebug.org/download.php

The latest Windows builds of PHP 7.4 ( specifically PHP 7.4 (7.4.0beta2) ) are built using VisualStudio VS16 (PHP Extension Build => API20190529,NTS,VS16) which is not accepted by the wizard.

I can see where to fix this in phpinfo-scanner.php, but I've got no ways of testing it.

I use MacOS and have not installed Xcode from the App Store, just the command line tools. Yet XDebug works just fine. I can't imagine how Xcode would actually be required for it to work... If it isn't, please correct the instructions which state the Mac prerequisites as

Xcode (from the App Store), and Xcode's command line tools

The full version of Xcode takes a huge amount of disk space. According to macpaw:

On the App Store page for Xcode, it lists the size of Xcode 12.5 as 11.7GB. However, when you try and install it, you'll get an error message unless you have at least 40GB of free space

There are many Chinese developers who can only read Chinese. So I'm trying to translate the documentation to Chinese and maintaining a mirror site with Chinese version documentation. Did that abuse any terms or copyright. Is it allowed?
Thanks for any comments.

On http://xdebug.org/docs/install#compile

(Debian users can install the required tools with apt-get install php5-dev)

is not true for Debian 10 (Buster) anymore. They just use prefix php for php7.3

vagrant@debian10:~$ apt search php-dev
Sorting... Done
Full Text Search... Done
php-dev/stable 2:7.3+69 all
  Files for PHP module development (default)

Hi Dereck,

I would like to suggest to create a step by step tutorial on how to get remote step debugging working for first time users. I hit the wall for many hours on how to get it working today and more times in the past. If you're open to such a contribution, I'll happily provide it.

In this page you can find between parenthesis this text at the end of the first paragraph of the "Configuring Step Debugging":

Skip to Activating the Debugger if that's the case.

The "Activating the Debugger" is a broken link.

Greeting , I was browsing the website, specially contributing web page, and figured out that in the third section of the web page :

Working on a new feature

the issue is with the naming as I guess,

Create a feature branch:
git checkout -b issue{issue number}

the question is : does that on purpose??

or it's just a typo and you need to update it to :

Create a feature branch:
git checkout -b feature{feature number}

and so on.

Regards.

PR derickr/dbgp#18 changed 'resolved_breakpoints' to opt-in feature but this change is not reflected at https://xdebug.org/docs/dbgp#feature-names

I am trying to get resolved breakpoints to work in NetBeans PHP debugger.
The only way how to get resolved attribute in breakpoint_set response was to call feature_set -n resolved_breakpoints -v 1.

Currently the RSS feed does not contain any items.

Seems like commit 5df9729 broke it because the path to the news items in rss.php did not get updated.

OS: win 10
Before I used Xdebug v2 with PHP 7.3 and it worked well.
Nowadays I work on a project(it needs php 7.4+) and so I installed another xampp version and configured everything in the same way as before. (using dll wizard)

Thanks in advance.

When I started to use v2.8.0 my test with code coverage (1282 tests) takes approx 1,5h compered to ~11min on v2.7.2.

env:
Docker php:7.3.11-fpm-alpine
Framework: Symofny 4.3 with simple-phpunit

Hello! I'm user of xdebug with the laravel projects and vscode.
I configured it a few times correctly with the wizard, but this time, with my new homestead vm, nothing was shown in the wizard page.

But now I found out the how to solve it.
I opened php -i output file named 'php -i' with notepad(in win10) but it was the bad operation and the problem. I tried post opening the file with my vscode, and it worked.

I'm not sure the problem but I can guess it because of difference of the character code... anyway I can now configure my new vm! I really like to say thank you very much to @derickr for helpfully asking me what's the problem!

When you run PHP v8.0 with Xdebug v3.0 enabled, JIT is not working regardless that Opcache is on. It seems that Xdebug is overriding zend_execute_ex() function and this seems to be the cause of the issue. The error message is following:

<br />
<b>Warning</b>:  JIT is incompatible with third party extensions that override zend_execute_ex(). JIT disabled. in <b>Unknown</b> on line <b>0</b><br />
[15-Sep-2021 12:00:00] NOTICE: fpm is running, pid 1
[15-Sep-2021 12:00:00] NOTICE: ready to handle connections

When Xdebug if off, both Opcache and JIT work fine.

I have also created repository, where you can easily reproduce the issue. Just follow the readme.

Repository is here: https://github.com/lukasneubauer/docker-php-circular-jit-dependency-dropped.

I just noticed that there is a wrong anchor link here: https://xdebug.org/docs/step_debug

In the section Introduction it says

(An overview of third party clients is available further down this page.)

and provides a link to https://xdebug.org/docs/step_debug#client but it should be the anchor #clients and not #client

I understand the distinction between "supported" and "unsupported" PHP versions, but the wizard at
https://xdebug.org/wizard.php is very confusing to people who want to find an xdebug version for "unsupported" PHP versions. We semi-regularly see questions like this on Stack Overflow: https://stackoverflow.com/q/52197962/476.

It would be more helpful to direct users with old PHP versions to the archives download page; or better, to tell them what old unsupported xdebug version fits their old unsupported PHP version.

Hi,

First of all, thank you for writing the documentation and the Xdebug.

I was reading the Xdebug documentation and I noted that it is not possible (at least with Google Chrome) to click on a section title and get the url with a suffix to that section. This is a good feature when we want to share a link to a specific topic.

Currently the website already uses anchors in some places but it is not allowed to select it unless you are poking around with "inspect element".

After reading the source code I noted that every section (not sure if is really all of them) has the following format

Page: https://xdebug.org/docs/upgrade_guide section Step Debugging

<a name="Step-Debugging"></a>
<h2>Step Debugging</h2>

If we change the format to

<a name="Step-Debugging" href="#Step-Debugging"><h2>Step Debugging</h2></a>

The styles of the tag a wll be applied to the h2 element but we will be able to click and get the url to that section: https://xdebug.org/docs/upgrade_guide#Step-Debugging

To remove the styles we can apply the following css

.section-anchor {
	color: black;
}
.section-anchor:hover {
	text-decoration: none;
}
.section-anchor:focus {
	outline: none;
}

and then add the css class .section-anchor

<a name="Step-Debugging" href="#Step-Debugging" class="section-anchor"><h2>Step Debugging</h2></a>

Currently there are 216 occurrences of the expression <a name=*.

After pasting my phpinfo(), I was prompted to add zend_extension = ext\php_xdebug-2.9.6-7.4-vc15-x86_64.dll to my php.ini.

This doesn't work; the correct line to use was zend_extension = php_xdebug-2.9.6-7.4-vc15-x86_64.dll.

My stock php.ini file appears to have extension_dir set to ext:

; Directory in which the loadable extensions (modules) reside.
; http://php.net/extension-dir
;extension_dir = "./"
; On windows:
extension_dir = "ext"

When pasting on this page
https://xdebug.org/wizard.php
a phpinfo() of PHP version 5.5.38

I get the following:"PHP versions below 5.5 are not supported."

The issue originates from
https://github.com/xdebug/xdebug.org/blob/master/html/include/phpinfo-scanner.php
on line 253 & 255

Hi Derick,
you may want to remove the asterix from the following file so that it checks out properly on Windows systems:

html/docs/include/settings/dump.*.html

When you git clone under windows, you get the following error:

error: unable to create file html/docs/include/settings/dump.*.html: Invalid argument

I was using Tailored Installation Instructions section of your website under following URL

https://xdebug.org/wizard.php

But, when i submitted php -i output and clocked Analyse my phpinfo() output button, it produces no result (blank output) i.e. not working. On the same page i found a link toward this piece of code that you are using to analyze phpinfo() output. But, it again did not work because of a PHP syntax error in your source code on following URL:

https://github.com/xdebug/xdebug.org/blob/master/html/include/phpinfo-scanner.php

Line 14 = '7.3' => [ 'src' => '2.7.0' 'win' => '2.7.0' ]

Line 14 (Fixed) = '7.3' => [ 'src' => '2.7.0', 'win' => '2.7.0' ]

error: unknown warning option '-Wdiscarded-qualifiers'; did you mean '-Wignored-qualifiers'? [-Werror,-Wunknown-warning-option]
error: unknown warning option '-Wlogical-op'; did you mean '-Wlong-long'? [-Werror,-Wunknown-warning-option]
error: unknown warning option '-Wmaybe-uninitialized'; did you mean '-Wuninitialized'? [-Werror,-Wunknown-warning-option]
error: unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-const-variable'? [-Werror,-Wunknown-warning-option]
make: *** [xdebug.lo] Error 1