It would seem that this bug has appeared again, in 5.0.1 on Apache 2.0.50
I've had a report about it on the firebird-php list, and on checking it
would seem that it can be reproduced.
Could someone have a look and see if we are right please.
--
Lester Caine
L.S.Caine Electronic Services
Lester Caine wrote:
It would seem that this bug has appeared again, in 5.0.1 on Apache 2.0.50
I've had a report about it on the firebird-php list, and on checking it
would seem that it can be reproduced.
Could someone have a look and see if we are right please.
Come on people - have two sites that have uninstalled PHP5 and returned
to 4 because of this problem. Do I just post it as a new bug?
--
Lester Caine
L.S.Caine Electronic Services
Lester Caine wrote:
It would seem that this bug has appeared again, in 5.0.1 on Apache 2.0.50
I've had a report about it on the firebird-php list, and on checking it
would seem that it can be reproduced.
Could someone have a look and see if we are right please.Come on people - have two sites that have uninstalled PHP5 and returned
to 4 because of this problem. Do I just post it as a new bug?
Hi Lester,
Why not follow up by submitting a bug report. Does apache leave
coredump files around?
There is notes on the bugs site on how to use gdb to get a backtrace
for debugging the issues.
Regards
--jm
--
Jacques Marneweck
http://www.powertrip.co.za/blog/
Jacques Marneweck wrote:
It would seem that this bug has appeared again, in 5.0.1 on Apache 2.0.50
I've had a report about it on the firebird-php list, and on checking it
would seem that it can be reproduced.
Could someone have a look and see if we are right please.Come on people - have two sites that have uninstalled PHP5 and returned
to 4 because of this problem. Do I just post it as a new bug?Why not follow up by submitting a bug report. Does apache leave
coredump files around?
Was not sure if it should be a new report or just reopen the old one -
not that I have ever actually used the bug site to enter stuff ;)
There is notes on the bugs site on how to use gdb to get a backtrace
for debugging the issues.
I'm getting feedback second hand at present. It would seem that the
problem is back in 4.3.9 and all versions of 5 so while it was
apparently fixed in 4.3.4 it has returned later. Sites are currently
running 4.3.1 and are stable, so I don't want to push it at that end.
--
Lester Caine
L.S.Caine Electronic Services