[xdebug-general] Re: stderr call

Ok, filed a bug report, but I cannot really find in the DGBP
documentation a clear explenation what features there are to handle errors.
And since this is the General list, maybe it would do good if there is a
small explenation for people who want to put error catching to their
small editors (like I did, because I hate reading the xml directly).

Suppose you want to catch

a) Parse errors (I doubt if it is possible)
b) Fatal errors like asking for a procedure of a nil pointer (or whatever)

So if one of these things is possible then what should start happening?

Me: stderr -i -1 -c 2
XDebug: ??? (could not find the XML syntax for "standard error or output
packages")

I suspect I might be in a really wrong track because in the xdebug code
I just see

DBGP_FUNC(stderr)
{
    xdebug_xml_add_attribute(*retval, "success", "0");
}

Thanks,
Hando Tint

>On Mon, 29 May 2006, Hando Tint wrote:
>
>
>
>>Could not find anything about in archives so I must be doing something really
>>wrong.
>>
>>Just after getting the init packet from debugger I do:
>>
>>stderr -i transaction_id -c 2
>>
>>result :
>>
>><response command="stderr" success="0" transaction_id="transaction_id">
>>
>>So I assume that this means the command did not go through.
>>And sure enough
>>
>><?
>>$s->a();
>>?>
>>
>>That should give a fatal error, but no messages come from the debugger after
>>hitting that line.
>>
>>Am I missing something or isn't that feature (catching fatal errors)
>>implemented?
>>
>>
>
>I think this should work, so can you please file a bug for it so that I
>can have a look (and don't forget about it?)
>
>regards,
>Derick
>
>
>
Received on Wed Jun 07 2006 - 10:49:46 BST