Wenn es um Performance-Debugging geht, gibt es eine Menge verfügbarer Werkzeuge. In den letzten Jahren habe ich nach einem gesucht, das wirklich leicht verwendbar ist und Engpässe selbst gut erkennt.

Es gibt einige, die spezifisch für WordPress sind, beispielsweise als Plugins, und einige für generelles Performance-Debugging in PHP. Andere wiederum benötigen eine bestimmte PHP-Erweiterung. Im folgenden Artikel decke ich alle möglichen Typen ab.

[…]

When it comes to performance debugging, there are a wide variety of tools available. The last years, I searched for one that is actually easily usable and provides easy access in identifying bottlenecks.

There are some that are specific to WordPress, e.g. as plugins, some allow general performance debugging via PHP and some require a PHP extension to be loaded. I’ll cover all of these types in the following article.

[…]

I'm thrilled to announce that I'll be speaking at the 23rd edition of #phpday, the international PHP conference in Italy, organised by @grusp.

I’ll be presenting a talk titled: "Better Debugging With Xdebug".

It's in Verona, Italy, on May 14-15th 2026.

You can use my speaker’s discount code "speaker_10OFF" for 10% off at https://www.phpday.it/tickets/?utm_medium=organic&utm_source=linkedin&utm_campaign=post-speaker

#PHP #Xdebug #Debugging

Last year I visited 2 big European CMS #flagship events.

One where a talk about sustainability was scheduled in a side event in a basement.
The other where a talk about this was scheduled in the regular main event scheme featuring a joint presentation from Drupal and Typo3 folks.
Also, in this the second event, had presentationf by #PHPUnit (Sebastian Bergman) and #xDebug (Derick Rethans).

Want to guess the #openSource #CMS - names from both events?

Me: "Why won't this app break on this line!?"

Also me: Helps to have #xdebug enabled if you're trying to debug something :blobcatfacepalm:

#php

A third-party #Composer plugin is breaking my Composer scripts and I can't trouble-shoot it because #PhpStorm is unable to step debug into Composer phar archive, even though 13yo blog articles suggest it should, and my command's code is not even called when the plugin is enabled. I can't find any setting related to this, and I don't want to fiddle with my setup to run Composer from source.
#php #xdebug

PSA: Do not accidentally hit the red button in PHPStorm.

Or, well... feel free to do so.

But it caused me 3 hours of debugging because suddenly my local dev environment ran into a timeout. Because PHP-FPM was waiting for PHPStorm to acknowledge the debugging session - which it didn'T do. And also didn't inform me that something was waiting.

So I was just left with an unresponsive PHP-FPM 🤯

I stumbled upon it because it worked in a different browser...

#php #xdebug #phpstorm

In this update I explain what happened with Xdebug development in the last month.

In the last month, I spent only around 9 hours on Xdebug, with 24 hours funded. The rest of the time, I spend on building out Xdebug Cloud version 2.

Xdebug 3.5

Most of this month I spent on a few bug and performance reports from the Xdebug 3.5 release — most notable a performance degradation on Windows due to the new experimental control sockets.

I also spent time on my large better code coverage patch, which still isn't quite as performant as the current feature; although it does give more precise results.

Native Path Mapping

Fabian Potencier, from Symfony fame, has created an exploratory patch for Twig to make use of Xdebug's new Native Path Mapping functionality.

From the initial patch, it became clear that a few things need to be improved on the Xdebug side for this to be a complete feature. For that reason, I have created a few issues to work on:

• Invent better way of configuring lots of line-to-line mappings

• Create xdebug_add_source_map_directory() function to dynamically add directories where Xdebug will load path mapping files from

• Add EOF marker/stanza to native path file mapper

My PhpStorm issue to allow for the setting of breakpoints in template file has now been merged, and is scheduled for 2026.1 EAP 2. At the time of writing this isn't quite out yet, so I will keep you posted.

Xdebug Videos

I have created one new videos in the last month:

• Xdebug 3: Interrupting Long Running Scripts with VS Code for Debugging

All Xdebug videos are now available on the phpc.tv PeerTube instance. This will be the primary location for new videos, although I also still post them to my YouTube channel.

If you have any suggestions, feel free to reach out to me on Mastodon or via email.

Xdebug Cloud

I am currently reworking Xdebug Cloud, the Proxy As A Service platform to allow for debugging in complex networking scenarios.

The new version will allow for automatic subscriptions.

Packages will start at £16/month for one-developer companies.

If you want to be kept up to date with Xdebug Cloud, please sign up to the mailing list, which I will use to send out an update not more than once a month.

Question about #php #xdebug
I have in parallel openTelemetry for tracing running on local. I would like to add a span, if xdebug stops for a breakpoint.
Is there any type of hook or magic possible/available?

Exit VSCode, enter #VSCodium, binary versions of the VSCode editor with all telemetry and tracking disabled by default.

It's a drop-in replacement for VSCode and has been working perfectly for me, including its #xdebug integration.

➡️ https://vscodium.com

debug tui can now accept a script as an argument and monitors the stdout/stderr. also blinking lights. #xdebug #php

https://github.com/dantleech/debug-tui

RE: https://phpc.social/@phpc_tv/115913656275791585

@phpc_tv wow so many vids in there! Awesome!

#php #phpc #composerphp #xdebug # #peertube

Schritt-für-Schritt-Anleitung fürs PHP Debugging mit Xdebug: 

Auf unserem Managed Server stellen wir die PHP-Erweiterung Xdebug zur Verfügung.

Xdebug ermöglicht es dir, deinen Code mit dem Setzen von Breakpoints oder der Überwachung von Variablen zu debuggen.

In unserem neusten Blogpost erklärt @Markus, wie du Xdebug einrichten und verwenden kannst.

Hier gehts zum Artikel: https://opsone.ch/de/blog/php-debugging-mit-xdebug

#xDebug #ManagedServer #OpenSource #SwissHosting #DevOps

The fact that the word #Docker isn't used anywhere on this page is fucking insane!
wtf are people using out there?

https://xdebug.org/funding/001-native-path-mapping

Anyway, in case you didn't notice: #php #Xdebug (finally) supports path mapping, something every tool should provide!

#Xdebug est maintenant disponible pour php 8.5 !

https://xdebug.org/docs/compat

In this update I explain what happened with Xdebug development in the last month.

In the last month, I spent around 28 hours on Xdebug, with 24 hours funded.

Xdebug 3.5

Most of this month I spent on making Xdebug 3.5 ready, to coincide with the release of PHP 8.5.

First there were a few bug reports from the alpha releases, and I found some issues with the new Native Path Mapping myself. I also fixed a crash bug, and released the last pre-release version: 3.5.0alpha3.

After that release, I worked with the author of the PHP Debug Adapter for Visual Studio Code to bring Xdebug's control sockets to Windows. This held up the release of Xdebug 3.5 a little, as we wanted to get this right.

With this, I also created documentation for the Xdebug Control tool, which can be used to talk to Xdebug to initiate debugging sessions, and to force pausing running code without setting a breakpoint beforehand. This is only available on Linux and Windows.

Documentation Upgrades

While working on the documentation for the Xdebug Control tool, I went down the rabbit hole, and revamped the layout of the documentation's front page too. Instead of a single list with bullet points, there are now sections, and some images depicting the different features.

I also added a section on Flame Graphs. This feature that I added in Xdebug 3.3 was not yet documented.

PIE and PECL

I also documented how to install Xdebug with PIE, the new installer for PHP extensions based around the packagist ecosystem.

PIE is replacing the legacy PECL tool and website. Installing Xdebug with PECL is no longer the preferred installation method. Using PIE is strongly recommended.

In the future, there will no longer be new versions of Xdebug uploaded to the PECL website. In the mean time, releases through PECL will be delayed.

Xdebug Videos

I have created no new videos in the last months.

All Xdebug videos can be watched on my channel.

If you have any suggestions, feel free to reach out to me on Mastodon or via email.

Business Supporter Scheme and Funding

On GitHub sponsors, I am currently 42% towards my $2,500 per month goal, which is set to allow continued of Xdebug.

If you are leading a team or company, then it is also possible to support Xdebug through a subscription.

In the last month, no new business supporters signed up.

Besides business support, I also maintain a Patreon page, a profile on GitHub sponsors, as well as an OpenCollective organisation.

If you want to contribute to specific projects, you can find those on the Projects page.

Xdebug Cloud

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, and I have recently introduced a package for larger companies. This has a larger initial set of tokens, and discounted extra tokens.

If you want to be kept up to date with Xdebug Cloud, please sign up to the mailing list, which I will use to send out an update not more than once a month.

I'm surprised there isn't more noise about #PhpStorm debugger showing PHP lazy objects used by #Doctrine as "Collecting data...". I wonder if there's something in our #Symfony or #PHP setup that triggers this bug and it's otherwise uncommon. It seems everything's alright at #Xdebug side, but there's hardly any movement in JetBrains issue tracker.

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!

#php #php85 #xdebug #debugging

It must be the first of the month, because the GitHub sponsor cancellations are coming in again.

Instead of spending money on things that you don't need on this #cybermonday, support the maintainers of the open source projects who help you create the software that powers your site.

For @Xdebug that could be through:
- GitHub sponsors: https://github.com/sponsors/derickr
- Directly with an invoice: https://xdebug.org/support
- Signing up and using Xdebug Cloud: https://xdebug.cloud/

#php #xdebug #sponsor

My current dev setup uses a dockerised PHP install, PHPStorm and Xdebug. This works fine as expected, but whenever I launch an async process that's picked up by a queue worker.. I lose the ability to use xdebug.

Is there something I'm missing in my setup that would indeed offer this functionality? Anyone else happen to have this setup working? Working with logs for debugging is becoming tedious, especially for batched and chained jobs.

#xdebug #phpstorm #docker #debugging