Prev: XSLTProcessor issue
Next: Will PHP ever "grow up" and have threading?
From: Peter Lind on 23 Mar 2010 07:16
Ahh, I see why my suggestions had no effect - I assumed you were
dealing with normal php errors, not something done customly by the
code.

I'm afraid the only option I see is that of debugging the problem
script to find out where it opens STDERR - if you're certain that the
script specifically outputs messages to STDERR, then it's opening that
stream somewhere before the output.

Regards
Peter

On 23 March 2010 11:28, Marten Lehmann <lehmann(a)cnm.de> wrote:
>> Have you tried with
>> http://dk2.php.net/manual/en/function.error-reporting.php or just the
>> @ operator?
>
> Yes. But this does not work, because error levels and the @ operator only
> relate to errors thrown by the PHP runtime and have nothing to do with
> STDERR.
>
> But I need a way to close the STDERR file handle at the beginning of a
> script or at least catch and remove all output sent to STDERR.
>
> Regards
> Marten
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--
<hype>
WWW: http://plphp.dk / http://plind.dk
LinkedIn: http://www.linkedin.com/in/plind
Flickr: http://www.flickr.com/photos/fake51
BeWelcome: Fake51
Couchsurfing: Fake51
</hype>
First  |  Prev  | 
Pages: 1 2
Prev: XSLTProcessor issue
Next: Will PHP ever "grow up" and have threading?