Debugging facilities

Some improvements to make life easier

Orkan	#11874 2009-04-29 03:01
Contributors	Ahh, I thought you're saying that it isnt possible to use XDebug through the web interface (only in external tools like NetBeans or Eclipse...) Yah, debugging on a production server isnt the best practice :p Anyway, it could be nice to have XDebug stack trace displayed on each server halt, like Symfony has, with last DB query used. MySQL error messages are the most irritating, they never show which query is causing problems. The most extreme example is something like: Error at '' PS. XDebug and Target Management for Eclipse (vid) Perl - the only language that looks the same before and after RSA encryption.
This post was edited by Orkan (2009-04-29 03:07, 15 years ago)

Orkan

#11874 2009-04-29 03:01

Ahh, I thought you're saying that it isnt possible to use XDebug through the web interface (only in external tools like NetBeans or Eclipse...)

Yah, debugging on a production server isnt the best practice :p
Anyway, it could be nice to have XDebug stack trace displayed on each server halt, like Symfony has, with last DB query used. MySQL error messages are the most irritating, they never show which query is causing problems. The most extreme example is something like: Error at ''

PS. XDebug and Target Management for Eclipse (vid)

Perl - the only language that looks the same before and after RSA encryption.

This post was edited by Orkan (2009-04-29 03:07, 15 years ago)