php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #40584 new Soapclient produces Segfault/Core dump
Submitted: 2007-02-21 19:53 UTC Modified: 2007-02-21 20:46 UTC
From: thejam at gmail dot com Assigned:
Status: Closed Package: SOAP related
PHP Version: 5.2.1 OS: SLES 10 (s390x) 64bit
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: thejam at gmail dot com
New email:
PHP Version: OS:

 

 [2007-02-21 19:53 UTC] thejam at gmail dot com
Description:
------------
First bug report, I've scoured the reports for similar issues, nothing is helping though.  Hopefully I didn't miss something.

Platform is zLinux VM on the mainframe.  SLES 10.

PHP installed from source, not through yast:

'./configure' '--enable-soap' '--without-pear' '--with-apxs2=/usr/local/apache2/bin/apxs'

-------------------
Declaring a new SoapClient throws a segfault when the script is processed.  In a browser, it immediately asks if you want to save the script.  Log files shows a Segmentation Fault.







Reproduce code:
---------------
<?

echo "Hello World!";

$sccSystem = new
SoapClient('http://myserver/services/sccsystem?wsdl');

?>

Expected result:
----------------
Hello World!

**I don't expect output from the SoapClient object, I whittled it down to just this line, and found it still segfaulted.**

Actual result:
--------------
Nothing.

Log file says:

[Wed Feb 21 13:21:32 2007] [notice] child pid 21118 exit signal Segmentation fault (11)

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-02-21 20:02 UTC] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.


 [2007-02-21 20:38 UTC] thejam at gmail dot com
Recompiled with --enable-debug, and no more segfault.  I've recompiled twice before, but I still think it was probably botched.  Thanks.
 [2007-02-21 20:46 UTC] tony2001@php.net
You can also try to recompile it with --disable-debug, but make sure CFLAGS contains "-O0 -g" otherwise you won't see any debug symbols.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Jul 24 15:01:29 2024 UTC