From:             e_p_17 at hotmail dot com
Operating system: CentOS
PHP version:      5.2.3
PHP Bug Type:     Unknown/Other Function
Bug description:  PHP crashes in the middle of a dumping an object

Description:
------------
I apologize in advance for the poor quality of this bug report. I can't
really give you any information on how to reproduce the problem because
this happened on a production server and we had to fix it ASAP with no time
to really troubleshoot.

We had been successfully running PHP 5.1.6, but decided to upgrade to
5.2.3. After upgrading, everything seemed to be working fine. However, we
later discovered that payment transactions via Paypal's Website Payments
Pro PHP SDK were not completing. 

Initially we thought it may have been Paypal or an incompatability between
Paypal's WPP SDK and PHP 5.2, however, our minimal investigation found
otherwise.

Using various script breaks and object dumps, we were able to succesfully
reproduce a PHP crash every time we attempted to run a var_dump on an
object created via one of the calls within the WPP SDK. The object was
created successfully, but when we tried to var_dump it, PHP would crash in
the middle of the var_dump operation.  

We know it's crashing because every time we tried to var_dump we would get
this in our error log: "exit signal Segmentation fault (11)" and the output
would simply terminate in a strange place like: "[_defaultObjectClassname]
=> stdClass ["

Note that no error messages are produced in the visible output - only the
error log.

Simply reverting back to PHP 5.1.6 (same ./configure options etc.) fixes
the problem.  

In my extremely limited wisdom, it almost seems like there's a memory/size
limit on the object itself (the object was quite large).

Again, my apologies for not being able to submit a better bug report. It
may not even be a bug, but I have never experienced anything like this
before and since reverting to 5.1.6 fixed the issue completely, I can only
assume it's something within the 5.2.3 build that's causing the problem.







-- 
Edit bug report at http://bugs.php.net/?id=41972&edit=1
-- 
Try a CVS snapshot (PHP 4.4): 
http://bugs.php.net/fix.php?id=41972&r=trysnapshot44
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=41972&r=trysnapshot52
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=41972&r=trysnapshot60
Fixed in CVS:                 http://bugs.php.net/fix.php?id=41972&r=fixedcvs
Fixed in release:             
http://bugs.php.net/fix.php?id=41972&r=alreadyfixed
Need backtrace:               http://bugs.php.net/fix.php?id=41972&r=needtrace
Need Reproduce Script:        http://bugs.php.net/fix.php?id=41972&r=needscript
Try newer version:            http://bugs.php.net/fix.php?id=41972&r=oldversion
Not developer issue:          http://bugs.php.net/fix.php?id=41972&r=support
Expected behavior:            http://bugs.php.net/fix.php?id=41972&r=notwrong
Not enough info:              
http://bugs.php.net/fix.php?id=41972&r=notenoughinfo
Submitted twice:              
http://bugs.php.net/fix.php?id=41972&r=submittedtwice
register_globals:             http://bugs.php.net/fix.php?id=41972&r=globals
PHP 3 support discontinued:   http://bugs.php.net/fix.php?id=41972&r=php3
Daylight Savings:             http://bugs.php.net/fix.php?id=41972&r=dst
IIS Stability:                http://bugs.php.net/fix.php?id=41972&r=isapi
Install GNU Sed:              http://bugs.php.net/fix.php?id=41972&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=41972&r=float
No Zend Extensions:           http://bugs.php.net/fix.php?id=41972&r=nozend
MySQL Configuration Error:    http://bugs.php.net/fix.php?id=41972&r=mysqlcfg

Reply via email to