Marcel van Duijn

Hello,

sorry for the late response, but thanks for your answer.

But what I’m trying to debug… Anything really. I also use a debugger to learn about the nitty gritty details of WP itself. Like tracing the execution stack to learn what code is triggered when, view variable and property values, etc etc.

I guess the real question is what in WP is causing the issue that you cannot seem to use a debugger properly? Also, this problem does not seem to relate to my PHP development environment (Zend Studio), cause I read posts about other environments having problems as well. Apart from not being able to trace the execution stack etc, another big disadvantage of having to use WP_DEBUG is that you have to actually write (and delete) the specific code that outputs the code you want to check.

Do you haveany idea what might be causing this debugging issue? And… what PHP and debug environment are the core developers using then?

Regards,

Marcel

I posted in 2 different forums, which is not so weird, as the subject was relevant for both. When I noticed one disappeared I reposted because I didnt know what happened with it.

I understand you dont want people to flood 1 forum with the same post, but posting the same topic in 2 forums is not so weird right?

Anyway, maybe you have an answer to my question? I spent the last 3 months studying WP, and already noticed debugging by stepping through the code was really slow. Which gets worse the deeper you want to dive in. But now that I end up in the backend and noticed stepping through code was plain impossible, this is kind of a shock.

It can’t seriously be so that you are supposed to use echo/print etc and other development plugins to develop for WordPress right? Can you tell me what’s the most efficient and thorough way to debug WP?

Regards