Hey list,
I really /really/ hate to cause additional noise on this list, but I'm
developing software in the PHP 5.3 snapshots with a timeline for release
around the same time this version of PHP is released. We always try to
keep current with our snapshots to make sure everything still works. My
development team has been grinded almost to a halt by the fact that any
thrown exception in the latest PHP 5.3 snapshots is causing Apache to crash.
There's already a bug report here: http://bugs.php.net/bug.php?id=44226
I know unreleased PHP versions can't be supported, but fundamental
language functionality was broken. This bug has been open for a month.
This seems like it would be a critical problem and I'm glad Jani had
already looked at and responded to the report. This is just slowing my
team down when the snapshots are generally pretty high quality, from my
personal experience. If this could be looked at further, I would gladly
help someone with debugging and testing and such, if they'll take a look
at the code.
Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex Corporation
Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.
Can you try a debug build with --enable-debug to get a more detailed
backtrace.
Also what is the exact configure line and which apache 2 model are you
using? Worker or Pre-fork?
Scott
Hey list,
I really /really/ hate to cause additional noise on this list, but
I'm developing software in the PHP 5.3 snapshots with a timeline for
release around the same time this version of PHP is released. We
always try to keep current with our snapshots to make sure
everything still works. My development team has been grinded almost
to a halt by the fact that any thrown exception in the latest PHP
5.3 snapshots is causing Apache to crash.There's already a bug report here: http://bugs.php.net/bug.php?
id=44226I know unreleased PHP versions can't be supported, but fundamental
language functionality was broken. This bug has been open for a
month. This seems like it would be a critical problem and I'm glad
Jani had already looked at and responded to the report. This is just
slowing my team down when the snapshots are generally pretty high
quality, from my personal experience. If this could be looked at
further, I would gladly help someone with debugging and testing and
such, if they'll take a look at the code.Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex CorporationPlease note: This message has been sent with information that could
be confidential and meant only for the intended recipient. If you
are not the intended recipient, please delete all copies and inform
us of the error as soon as possible. Thank you for your cooperation.
Hi Scott,
Scott MacVicar wrote:
Can you try a debug build with --enable-debug to get a more detailed
backtrace.Also what is the exact configure line and which apache 2 model are you
using? Worker or Pre-fork?Scott
Hey list,
I really /really/ hate to cause additional noise on this list, but
I'm developing software in the PHP 5.3 snapshots with a timeline for
release around the same time this version of PHP is released. We
always try to keep current with our snapshots to make sure everything
still works. My development team has been grinded almost to a halt by
the fact that any thrown exception in the latest PHP 5.3 snapshots is
causing Apache to crash.There's already a bug report here: http://bugs.php.net/bug.php?id=44226
I know unreleased PHP versions can't be supported, but fundamental
language functionality was broken. This bug has been open for a
month. This seems like it would be a critical problem and I'm glad
Jani had already looked at and responded to the report. This is just
slowing my team down when the snapshots are generally pretty high
quality, from my personal experience. If this could be looked at
further, I would gladly help someone with debugging and testing and
such, if they'll take a look at the code.Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex CorporationPlease note: This message has been sent with information that could
be confidential and meant only for the intended recipient. If you are
not the intended recipient, please delete all copies and inform us of
the error as soon as possible. Thank you for your cooperation.
I mentioned it in my response to the bug report, but forgot to mention
it here. I'm just using pre-built Windows Binaries for each. I'm on
Windows XP Pro with SP2. Using Apache 2.2.8. Not sure what the exact
Apache model is.
Thanks for looking into this for me.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex Corporation
Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.
Jeremy Privett wrote:
Hi Scott,
Scott MacVicar wrote:
Can you try a debug build with --enable-debug to get a more detailed
backtrace.Also what is the exact configure line and which apache 2 model are
you using? Worker or Pre-fork?Scott
Hey list,
I really /really/ hate to cause additional noise on this list, but
I'm developing software in the PHP 5.3 snapshots with a timeline for
release around the same time this version of PHP is released. We
always try to keep current with our snapshots to make sure
everything still works. My development team has been grinded almost
to a halt by the fact that any thrown exception in the latest PHP
5.3 snapshots is causing Apache to crash.There's already a bug report here: http://bugs.php.net/bug.php?id=44226
I know unreleased PHP versions can't be supported, but fundamental
language functionality was broken. This bug has been open for a
month. This seems like it would be a critical problem and I'm glad
Jani had already looked at and responded to the report. This is just
slowing my team down when the snapshots are generally pretty high
quality, from my personal experience. If this could be looked at
further, I would gladly help someone with debugging and testing and
such, if they'll take a look at the code.Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex CorporationPlease note: This message has been sent with information that could
be confidential and meant only for the intended recipient. If you
are not the intended recipient, please delete all copies and inform
us of the error as soon as possible. Thank you for your cooperation.I mentioned it in my response to the bug report, but forgot to mention
it here. I'm just using pre-built Windows Binaries for each. I'm on
Windows XP Pro with SP2. Using Apache 2.2.8. Not sure what the exact
Apache model is.Thanks for looking into this for me.
Hey Scott and list,
I wanted to check on this issue to see if anyone was actively working on
it and see what I could do to help.
Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex Corporation
Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.
Jeremy Privett wrote:
Jeremy Privett wrote:
Hi Scott,
Scott MacVicar wrote:
Can you try a debug build with --enable-debug to get a more detailed
backtrace.Also what is the exact configure line and which apache 2 model are
you using? Worker or Pre-fork?Scott
Hey list,
I really /really/ hate to cause additional noise on this list, but
I'm developing software in the PHP 5.3 snapshots with a timeline
for release around the same time this version of PHP is released.
We always try to keep current with our snapshots to make sure
everything still works. My development team has been grinded almost
to a halt by the fact that any thrown exception in the latest PHP
5.3 snapshots is causing Apache to crash.There's already a bug report here:
http://bugs.php.net/bug.php?id=44226I know unreleased PHP versions can't be supported, but fundamental
language functionality was broken. This bug has been open for a
month. This seems like it would be a critical problem and I'm glad
Jani had already looked at and responded to the report. This is
just slowing my team down when the snapshots are generally pretty
high quality, from my personal experience. If this could be looked
at further, I would gladly help someone with debugging and testing
and such, if they'll take a look at the code.Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex CorporationPlease note: This message has been sent with information that could
be confidential and meant only for the intended recipient. If you
are not the intended recipient, please delete all copies and inform
us of the error as soon as possible. Thank you for your cooperation.I mentioned it in my response to the bug report, but forgot to
mention it here. I'm just using pre-built Windows Binaries for each.
I'm on Windows XP Pro with SP2. Using Apache 2.2.8. Not sure what the
exact Apache model is.Thanks for looking into this for me.
Hey Scott and list,
I wanted to check on this issue to see if anyone was actively working
on it and see what I could do to help.Thanks.
Another week later and still no response. I would hope /someone/ thinks
this a critical issue and needs to be resolved. Is /anyone/ looking at
this at all?
Thanks.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex Corporation
Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.
Jeremy Privett wrote:
Another week later and still no response. I would hope /someone/ thinks
this a critical issue and needs to be resolved. Is /anyone/ looking at
this at all?Thanks.
The line that is crashing was last changed by Dmitry on January 24th,
see http://php.markmail.org/message/7egzhpab6reff7lj
I can't see any errors with valgrind.
Any idea Dmitry?
Scott
Scott MacVicar wrote:
Jeremy Privett wrote:
Another week later and still no response. I would hope /someone/
thinks this a critical issue and needs to be resolved. Is /anyone/
looking at this at all?Thanks.
The line that is crashing was last changed by Dmitry on January 24th,
see http://php.markmail.org/message/7egzhpab6reff7ljI can't see any errors with valgrind.
Any idea Dmitry?
Scott
Thank you, Scott.
The problem only seems to occur in Apache. Trying to reproduce in CLI or
in IIS using ISAPI results in no problems. I've tested from Apace 2.2
all the way back to Apache 1.3.39 and get the same result. I can have a
friend of mine test the issue in Linux to make sure it's not just a
Windows issue. I'll get back to you about that.
--
Jeremy Privett
C.E.O. & C.S.A.
Omega Vortex Corporation
Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.
The problem only seems to occur in Apache. Trying to reproduce in CLI or in
IIS using ISAPI results in no problems. I've tested from Apace 2.2 all the
way back to Apache 1.3.39 and get the same result. I can have a friend of
mine test the issue in Linux to make sure it's not just a Windows issue.
I'll get back to you about that.
I get the problem with Sambar Server V7.0 using ISAPI.
--
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
Hi Scott,
Could you provide a script to reproduce the crash?
Thanks. Dmitry.
Scott MacVicar wrote:
Jeremy Privett wrote:
Another week later and still no response. I would hope /someone/
thinks this a critical issue and needs to be resolved. Is /anyone/
looking at this at all?Thanks.
The line that is crashing was last changed by Dmitry on January 24th,
see http://php.markmail.org/message/7egzhpab6reff7ljI can't see any errors with valgrind.
Any idea Dmitry?
Scott
Dmitry Stogov wrote:
Hi Scott,
Could you provide a script to reproduce the crash?
Thanks. Dmitry.
Scott MacVicar wrote:
Jeremy Privett wrote:
Another week later and still no response. I would hope /someone/
thinks this a critical issue and needs to be resolved. Is /anyone/
looking at this at all?Thanks.
The line that is crashing was last changed by Dmitry on January 24th,
see http://php.markmail.org/message/7egzhpab6reff7ljI can't see any errors with valgrind.
Any idea Dmitry?
Scott
http://bugs.php.net/bug.php?id=44226
<?php
throw new Exception;
?>
That's all you need - throwing any type of exception makes it blow up