I have installed NB 7.1, WAMPP 1.7.7 (with PHP 5.3.8) and XDebug 2.1.4. I can inspect variables on breakpoints, ok. But if exception occurs then Netbeans dont know about this, while browser show xdebug-formatted callstack. NB still thinks "netbeans-xdebug" is "running". So my question is: can Netbeans report a PHP exception?
I prepare this code for testing:
<?php
function exceptionHandler($ex) {
echo 'Uncaught exception: ', $ex->getMessage(), "
"; // BREAKPOINT
}
set_exception_handler('exceptionHandler');
function errorHandler($errno, $errstr, $errfile, $errline) {
throw new ErrorException($errstr, 0, $errno, $errfile, $errline);
}
set_error_handler('errorHandler');
throw new Exception;
phpinfo();
?>
Netbeans stops and report on my breakpoint, so one problem solved. But NB immadietly show alert titled "Socket Exception" with text:
Socket Exception occured
If you have ane Watches, try to remove them and restart debugger. If removing Watches doesn't help or you don't have any Watches, please file an issue and provide the exact steps to reproduce your problem. Please attach the IDE log. Attaching your project would also be very helpful.
I think that PHP terminates when exception occurs, so xdebug must stop and Netbeans loses dubbuging data.
When you start Debug mode in Netbeans and an unhandled exception gets through then it outputs to your browser just like it would if you weren't running a debugger.
Netbeans doesn't magically catch them. i.e. you can't analyze them the same way you can look at the contents of variables.
The "netbeans-xdebug" is "running" still shows up because it is in fact still running and will continue to run until you stop it yourself or the debug session has some serious error occur, which probably won't be php related. Usually if a major error occurs you'll get some popup window. If you stop it yourself then netbeans will create a new tab in your browser saying the xdebug session has ended.
If you hit refresh in your browser then netbeans will catch the request and analyze it and if you've setup break points it will stop at the break points. After that request has been serviced, if you hit refresh again, netbeans will keep catching any requests that come in.
Edit : One thing I found on the xdebug site that might help you in a way with exceptions in the following option.
xdebug.show_exception_trace
Type: integer, Default value: 0
When this setting is set to 1, Xdebug will show a stack trace whenever
an exception is raised - even if this exception is actually caught.
You can set this option in your php.ini file in the xdebug section.
One workaround for this situation is to use the set_error_handler() function to set a custom error handler, and then set a breakpoint inside that custom error handler. When an error occurs, netbeans will stop at your breakpoint and you'll have full access to the Call Stack where you can look at any variables at the time of the error.