On Thu, 15 Mar 2007, Jun Monnai wrote:
> > That indeed seems to be a bug, could you file a bug report at
> > http://bugs.xdebug.org for this please?
>
> Thanks, I did.
It's fixed now, thanks for the report.
> > The client can do that, but only a limited number of functions is
> > available:
>
> First, I wish xdebug stops the execution and send status to the debug
> client with <response command="run" ... reason="error"> or something
> when an error happens.
>
> The current version (2.0.0RC4-dev) does not stop the executsion,
> so there is no way for the debug client to know error.
>
> > breakpoint_list, context_names, feature_get, typemap_get, status and
> > xcmd_profiler_name_get.
>
> When an error occurs, if possible, people want to see variables and
> stacks to see what was bad.
You can still do that, but you will have to set a breakpoint on the
error type, something like:
breakpoint_set -i 1 -t exception -x "Fatal error"
regards,
Derick
-- Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.orgReceived on Sun Mar 18 2007 - 10:13:33 GMT
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST