ramsey, to php
@ramsey@phpc.social avatar

I’m trying to run “Debug” (for step-debugging with ) in while running a test. I do this all the time with standard tests, and I’ve never had this problem…

The test runner stops immediately, and PhpStorm reports in the debug console, “Test framework quit unexpectedly.”

Has anyone else seen this error? Do you know what causes it?

asgrim, to Java
@asgrim@phpc.social avatar

I got a Stream Deck delivered today and started playing around with it already, very handy for step debugging! I have several other ideas already to improve my workflow too... #streamdeck #stepdebugging #java #rustlang #php #xdebug #clang #gdb

ramsey, to random
@ramsey@phpc.social avatar

Did #PhpStorm recently change the way it connects to #Xdebug when executing tests from PhpStorm? I’m no longer able to get the debugger panel to work for a project that I’ve never had a problem using Xdebug in.

koehnlein, (edited ) to random
@koehnlein@mastodon.social avatar

Some time ago I had to develop a feature for a Neos CMS project and wanted to use @Xdebug - as I always do it in our @ddev projects. But it turned out to need a bit more configuration.

I finally wrote a blog post about why Neos CMS is different from other PHP software and how I managed to use Xdebug almost the way I'm used to.

https://www.koehnlein.eu/en/blog/2024/xdebug-neos-ddev-phpstorm/

I would really appreciate your feedback.

sebastian, to php
@sebastian@phpc.social avatar

The extension optimizes bytecode.

Extensions for collecting code coverage data such as operate on this bytecode.

Naturally, whether or not bytecode optimization is performed has an impact on the code coverage data that is collected.

I kn(e|o)w this. But such a difference just really surprised me for the first time.

Code Coverage reported with bytecode optimization enabled

derickr, to php
@derickr@phpc.social avatar

📰 New blog post: "Xdebug at 21": https://derickrethans.nl/xdebug-21.html #php #xdebug #OpenSource

Crell, to php
@Crell@phpc.social avatar

Oh good. The latest PHPStorm/IntelliJ update broke all of my configurations. That's nice of them.

derickr, to php
@derickr@phpc.social avatar

This week has been a "find one bug, fix one bug, find another bug" kinda week in @Xdebug land. I'm now on the 5th one, I think.

#php #debugging #xdebug

nanawel, (edited ) to php French

Following a request from me and some colleagues, my company is about to become a (hopefully) significant supporter and contributor of @derickr, awesome creator and maintainer of @Xdebug 🥳

As a daily developer, it's a tool I could not work without, so I'm happy we could do a little bit to help. 💪

cybersmog, to random
@cybersmog@phpc.social avatar

Today @Xdebug helped me to locate a bug introduced by a stupid typo by me in a configuration file. My brain parser failed to detect that typo. Nevertheless it took me way too long to eventually hunt down the error.
Big kudos for this great tool! #xdebug

SenseException, to php German
@SenseException@phpc.social avatar

$ docker run -it third_party_image sh

php -r 'echo 1;'

segmentation fault

Xdebug, to php

🎉 Xdebug 3.3.0alpha3 Released!

🔥 This alpha release introduces flamegraphs and the step debugger optimisations that @derickr wrote about.

🔗 https://xdebug.org/announcements/2023-10-19

🐘 @Xdebug

sebastian, to php
@sebastian@phpc.social avatar

Over the last few months, I've been asked time and again:

"Sebastian, which PHP extension do you use to collect code coverage data?"

This question may sound simple, but to answer it I'm afraid I need to elaborate a little ...

https://thephp.cc/articles/pcov-or-xdebug?ref=mastodon

michael, to php
@michael@thms.uk avatar

TIL about xrDebug. Am I the only one who finds it weird that someone would create a debugger for that uses an extremely minor variation in name of the popular extension?

https://www.reddit.com/r/PHP/s/KbrSZFHHOk

ramsey, to php
@ramsey@phpc.social avatar

This is a pretty cool package, if you use #Twig with #PHP and #Xdebug. https://github.com/ajgarlag/AjglBreakpointTwigExtension

derickr, to php
@derickr@phpc.social avatar

:xdebug: I've spent more time optimising Xdebug's debugger. This time I focussed on breakpoints.

🚫 Before these changes, Xdebug would check after every statement for line breakpoints.

✔️ Now, it only checks for them, if we already have concluded that the function contains any breakpoint.

🎈 This means that setting a breakpoint incurs a small performance impact, while almost no impact exists while running your PHP code.

🆕 To sponsor my work: https://xdebug.org/support

outofcontrol, to vscode
@outofcontrol@phpc.social avatar

Suddenly VSCode and PHPStorm’s Laravel Tinker stop executing code. CLI still worked fine. After the loss of much hair, I realized I had inadvertently clicked on the itsy bitsy little bug in PHPStorm and had enabled debugging. It was at this point I learned that enabling in also enabled it in !

KaffDaddy, to neovim German
@KaffDaddy@chaos.social avatar

Geil! Ich kann mit neovim debuggen!

derickr, (edited ) to php
@derickr@phpc.social avatar

📰 New blog post: "Flamboyant Flamegraphs", in which I show to use Xdebug 3.3's new flamegraph feature

https://derickrethans.nl/flamboyant-flamegraphs.html

derickr, to php
@derickr@phpc.social avatar
MelvilleSpence, to random
@MelvilleSpence@phpc.social avatar

Just as well is so useful, otherwise there would be a bounty on it. Damn thing was working last night, now it isn’t 😂

derickr, to php
@derickr@phpc.social avatar

🎉 I've just released @Xdebug 3.3.0alpha2, with preliminary support for PHP 8.3.

🔗 https://xdebug.org/announcements/2023-09-06

:xdebug: It also adds some functionality to xdebug_get_function_stack(), more about that later!

🐛 Uploading it to PECL didn't work, as due to an upgrade, MySQL now (finally) rejects characters that the table charset wouldn't allow, instead of just corrupting it. That took two hours to debug and fix. PECL will warn now → https://github.com/php/web-pecl/commit/cf57e9370820fa7738c782a751b47de713e0c3be

derickr, (edited ) to php
@derickr@phpc.social avatar

📽️ New video: "Xdebug 3.3: Flamegraphs", in which I show to use Xdebug 3.3's new flamegraph feature

https://youtu.be/4EocpeKxI0k

derickr, to php
@derickr@phpc.social avatar

ICYMI: New blogpost: "Concealed Code": https://derickrethans.nl/concealed-code.html

helmutstrasser, to random

#PHPStorm is a pretty darn good software, but sometimes I lose my nerve on settings and system notices. Especially #xdebug and the "Debug session was finished without being paused" message took me hours to figure out what is going on. "It may be caused by path mappings misconfiguration" is totally misleading. Most of the time it's simply because a breakpoint has been set for a code never been executed. 😞 🙄

  • All
  • Subscribed
  • Moderated
  • Favorites
  • provamag3
  • thenastyranch
  • magazineikmin
  • ethstaker
  • InstantRegret
  • tacticalgear
  • rosin
  • love
  • Youngstown
  • slotface
  • ngwrru68w68
  • kavyap
  • cubers
  • DreamBathrooms
  • megavids
  • mdbf
  • modclub
  • GTA5RPClips
  • normalnudes
  • khanakhh
  • everett
  • cisconetworking
  • osvaldo12
  • anitta
  • Leos
  • Durango
  • tester
  • JUstTest
  • All magazines