I'd tag it unreproducible and close it.
If there really is a bug, someone is likely to reproduce it and report
it again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, Jul 30, 2007 at 11:45:55AM +0200, Olaf van der Spek wrote:
I'd tag it unreproducible and close it.
If there really is a bug, someone is likely to reproduce it and report
it again.
No you tag it unreproducible when you have genuinely tried to
reproduce it, thing that I didn't do. I
[EMAIL PROTECTED]:~ - 2006-08-20 19:33:20: (mod_fastcgi.c.1048) the
fastcgi-backend /usr/bin/php4-cgi failed to start:
2006-08-20 19:33:20: (mod_fastcgi.c.1063) terminated by signal: 11
2006-08-20 19:33:20: (mod_fastcgi.c.1068) to be exact: it seg-fault,
crashed, died, ... you get the idea.
On Sun, Jul 29, 2007 at 04:30:21PM +0200, Olaf van der Spek wrote:
[EMAIL PROTECTED]:~ - 2006-08-20 19:33:20: (mod_fastcgi.c.1048) the
fastcgi-backend /usr/bin/php4-cgi failed to start:
2006-08-20 19:33:20: (mod_fastcgi.c.1063) terminated by signal: 11
2006-08-20 19:33:20:
It still doesn't look the same.
In the Debian bug report, PHP crashes while in the upstream bug report,
Lighttpd crashes.
But anyway, can you reproduce the bugs? Then it's a lot easier to fix.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
On Mon, Jul 30, 2007 at 12:10:11AM +0200, Olaf van der Spek wrote:
It still doesn't look the same.
In the Debian bug report, PHP crashes while in the upstream bug report,
Lighttpd crashes.
But anyway, can you reproduce the bugs? Then it's a lot easier to fix.
I've not had the time to try
6 matches
Mail list logo
