Bug #63516 [Opn]: The Process exits random with SEGV
Edit report at https://bugs.php.net/bug.php?id=63516&edit=1
ID: 63516
User updated by: dpeuscher at gmail dot com
Reported by: dpeuscher at gmail dot com
Summary: The Process exits random with SEGV
Status: Open
Type: Bug
-Package: Apache2 related
+Package: SOAP related
Operating System: openSUSE 11.0 (X86-64)
PHP Version: 5.4.8
Block user comment: N
Private report: N
New Comment:
Accidentally changed the package to apache2-related, sorry.
Previous Comments:
------------------------------------------------------------------------
[2013-06-06 15:57:51] dpeuscher at gmail dot com
Have you tried the WSDL_CACHE_DISK caching method instead of WSDL_CACHE_BOTH?
------------------------------------------------------------------------
[2013-06-06 11:25:48] arjen at react dot dom
I can confirm this under 5.4.15, got the same backtrace using the testscript.
------------------------------------------------------------------------
[2012-11-15 14:16:07] dpeuscher at gmail dot com
That was a great hint. I got it isolated! It seams like the problem occurs when the ini-option
wsdl_cache is set to 3 (WSDL_CACHE_BOTH), maybe also 2 (WSDL_CACHE_MEMORY). I
initialized 5 WSDL-Files that are nearly empty (just to don't throw any exceptions like
"Could not find any usable binding services in WSDL.". They all look like this:
http://pastebin.com/e6QBUkeh (Wasn't allowed to put
it in here because of possible Spam)
with 5 different names. I named them s1.wsdl, ... s5.wsdl. Afterwards I initialized an
ebay-Webservice. The test-Script looks like this:
http://pastebin.com/dWxg1qL7
Sometimes the SEGV appears after 50 calls, sometimes on the first call. It doesn't apper on
WSDL_CACHE_DISK or WSDL_CACHE_NONE.
------------------------------------------------------------------------
[2012-11-15 00:00:05] felipe@php.net
Please, try isolating the SOAP related part of code.
------------------------------------------------------------------------
[2012-11-14 15:48:00] dpeuscher at gmail dot com
I know that it is important for you to replicate the bug but I really have no clue
how to find the snippet that is the problem. Can you guess at which part I should
take a deeper look depending on the backtrace? Or telling me the environment I
need to analyse in gdb? Especially with the using of the Zend Framework it might
be nearly impossible to get the part.
I would like to give a better example but doesn't really know how.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=63516
--
Edit this bug report at https://bugs.php.net/bug.php?id=63516&edit=1
Thread (10 messages)