Xdebug Update: December 2020
Another monthly update where I explain what happened with Xdebug development in this past month. These will be published on the first Tuesday after the 5th of each month.
Patreon and GitHub supporters will get it earlier, on the first of each month.
You can become a patron or support me through GitHub Sponsors. I am currently 82% towards my $1,000 per month goal. If you're already supporting Xdebug's development, could you do me a favour and tweet this out?
Using @xdebug? Help its developer @derickr to get to 100% on his GitHub sponsors goal: https://github.com/sponsors/derickr #Xdebug3
If you are leading a team or company, then it is also possible to support Xdebug through a subscription.
In December, I worked on Xdebug for about 46 hours, with funding being around 30 hours. I worked mostly on the following things:
Releases
A few bugs were found in Xdebug 3.0.0, which should not come as a surprise, as with any big .0 release, users always find things that go wrong. December saw the 3.0.1 release, and the 3.0.2 released followed in the new year.
Xdebug 3.0.1 fixed several crashes and other bugs that are present in Xdebug 3.0.0. The crash when removing a breakpoint (or run-to-cursor) was the most notable fix in this release.
You'll have to wait for the January 2021 wrap up to find out about the 3.0.2 release, or you can have a look at the release announcement.
There are also new release of PhpStorm and the VS Code Plugin to address a few Xdebug related issues from their sides. On top of that, the GitHub repository of the VS Code Plugin has been moved to the Xdebug organisation. There is a back log of pull requests and issues that need looking at.
Xdebug Cloud
I have been continuing to test Xdebug Cloud, and I am working with a few private alpha testers. They're putting the hosted Cloud service through its paces.
At the same time I am working with a designer to make the https://cloud.xdebug.com look pretty too.
If you want to be kept up to date with Xdebug Cloud, please sign up to the mailinglist, which I will use to send out an update not more than once a month.
Business Supporter Scheme and Funding
In December, no new supporters signed up, but I would like to thank Automattic, CHECK24, e3N, Edmonds Commerce, Find My Electric, Intracto, JetBrains, Private Packagist, Seravo, Strategery, Supermetrics, TYPO3 GmbH, and Tideways for their support during 2020.
If you, or your company, would also like to support Xdebug, head over to the support page!
Besides business support, I also maintain a Patreon page and a profile on GitHub sponsors.
Life Line
If we must show off a little…
In more info innocent times, the hat riots caused some spankings...
100 Years Ago Men and Boys Fought on the Streets of New York Over Wearing Straw Hats Past Summer | The New York Public Library
https://www.nypl.org/blog/2022/09/23/straw-hat-riots-nycI hiked 15.5km in 3h12m14s
📷 Mushroom Village
🚩 Weg van den Prins Willemsberg, Ellecom, Nederland
I walked 2.4km in 59m34s
📷 National Cycle Network 6
🚩 Watford, United Kingdom
I walked 7.6km in 1h54m50s
📷 Tufted Duck Pair
🚩 Outer Circle, City of Westminster, United Kingdom
RE: https://phpc.social/@Xdebug/115662135830755552
I have just released Xdebug 3.5.0!
In the next few weeks I will create some content (text, and perhaps video) highlighting some new features in more detail.
Please share it with the world!
The master branch is now for Xdebug 3.6, targetting PHP 8.6
Back to -dev
Tweak release instructions a little
Go with 3.5.0
Tweak message IDs and severities for control socket log entries
I walked 8.1km in 1h26m40s
I walked 1.1km in 9m28s
I walked 8.5km in 1h30m56s
My whisky of the month for December 2025, is a 15yo Aultmore bottled by Cadenhead's.
Fixed off-by-one error in address length name for control socket on L…
Merged pull request #1050





Shortlink
This article has a short URL available: https://drck.me/xdebug-20dec-g7y