Re: when PHP code causes crash due to bad input, is it a bug?
| From: | Christian Stocker | Date: | Sat, 11 Jan 2003 09:37:02 +0000 |
| Subject: | Re: when PHP code causes crash due to bad input, is it a bug? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-93329@lists.php.net to get a copy of this message | ||
Am Freitag, 10.01.03 um 21:02 Uhr schrieb gk:
I am trying to help with PHP. But this experience makes me feel like it is not worth it. Can anyone give me some clarification. Is there a common agreement on what constitutes a bug? I have worked as Sr. SQA engineer for many years and have always worked under the understanding that crashes are unacceptible - no matter what caused them: code should be able to handle bad data and not crash. See my bug report and analysis by Daniel Veillard of libxml2 at: http://bugs.php.net/bug.php?id=21477Greg, don't make that big fuss about it. I fixed the code 15 minutes after bogusfying your report, so it throws an error, if the input is bad. Maybe setting it to bogus was a little bit too unfair, but my additional comments should have clarified it... chregu
- GregDate: Fri, 10 Jan 2003 11:50:35 -0800 To: sniper@php.net From: gk <gk@proliberty.com> Subject: Re: Bug #21477 [Opn->Bgs]: $node->dump_node($node) crashes with libxml2-2.4.30 At 06:54 PM 1/10/2003 +0000, you wrote:- Greg Keraunen -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.phpYou're not in position to decide what is bogus and what is not. This is bogus.