As first task in February I released Xdebug 3.1.3 which addressed a bug with the debugging protocol's eval command and exceptions, an issue with the debugger generating invalid XML, and a memory leak and performance issue with tracing.

Since then I have worked on triaging and fixing a few more issues. These have currently not been merged due to changes in GitHub Action's Windows support. I expect that to be resolved by the time you read this.

Fixes include a crash while using closures and static properties, something that Symfony Cache seems to use a lot, some memory leaks, and an issue with the legacy XDEBUG_SESSION_START trigger. I expect Xdebug 3.1.4 to be released imminently.

In the previous update I wrote about what I had in mind for this coming year. From feedback to this communique, and a highly scientific Twitter poll I've decided to prioritise the following items:

1. Creating an Xdebug Course: explaining in great detail how Xdebug works, how you use it, how you can get the most out of it, and many scenarios on how to set-up debugging in different environments. This needs to go beyond referential documentation pages, and will hence become a combined set of videos and tutorials, with examples and work-along exercises.

2. Xdebug Recorder and Player: A new feature in Xdebug which would allow for a full request to be stored in a file, including every intermediate state. Combined with a player, which would allow for replaying the request and interrogating every variable at every point during the execution of said script, through the debugging protocol and interacting with your IDE. The recorded files would be self contained, without needing access to the (original) source code. Besides "step over" it would also have a "step back", and perhaps even a slider to slide back and forwards through time.

I have started making an outline for the Course, and a prototype for the Recorder and Player.

Let me know if you have ideas about which specific topics the Course should offer.

Xdebug Cloud is the Proxy As A Service platform to allow for debugging in more scenarios, where it is hard, or impossible, to have Xdebug make a connection to the IDE. It is continuing to operate as Beta release. Packages start at £49/month.

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.

I have published one more video on how to use Xdebug on my YouTube channel.

• Debugging Unit Tests with PhpStorm explains how to use PhpStorm to debug Unit Tests, following a question on Twitter.

In February, no new business supporter signed up.

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.