@robocoder opened this Issue on December 3rd 2011 Contributor

It's been a while since we've tested with 5.1.x, and it looks like we have a regression.

DataTable.test.php segfaults:


(gdb) bt
<a href='/0'>#0</a>  0x08356392 in zend_std_unset_property ()
<a href='/1'>#1</a>  0x083835fc in ZEND_UNSET_OBJ_SPEC_UNUSED_CONST_HANDLER ()
<a href='/2'>#2</a>  0x0835c4c5 in execute ()
<a href='/3'>#3</a>  0x08332acc in zend_call_function ()
<a href='/4'>#4</a>  0x0834f565 in zend_call_method ()
<a href='/5'>#5</a>  0x08354911 in zend_objects_destroy_object ()
<a href='/6'>#6</a>  0x08357a26 in zend_objects_store_del_ref ()
<a href='/7'>#7</a>  0x0833b81d in _zval_dtor_func ()
<a href='/8'>#8</a>  0x08358f82 in _zval_dtor ()
<a href='/9'>#9</a>  0x0835b0c1 in zend_assign_to_variable ()
<a href='/10'>#10</a> 0x0837fd09 in ZEND_ASSIGN_DIM_SPEC_VAR_CV_HANDLER ()
<a href='/11'>#11</a> 0x0835c4c5 in execute ()
<a href='/12'>#12</a> 0x0835ca0c in zend_do_fcall_common_helper_SPEC ()
<a href='/13'>#13</a> 0x0835cdfc in ZEND_DO_FCALL_BY_NAME_SPEC_HANDLER ()
<a href='/14'>#14</a> 0x0835c4c5 in execute ()
<a href='/15'>#15</a> 0x0835ca0c in zend_do_fcall_common_helper_SPEC ()
<a href='/16'>#16</a> 0x0835cdfc in ZEND_DO_FCALL_BY_NAME_SPEC_HANDLER ()
<a href='/17'>#17</a> 0x0835c4c5 in execute ()
<a href='/18'>#18</a> 0x08332acc in zend_call_function ()
<a href='/19'>#19</a> 0x0834f565 in zend_call_method ()
<a href='/20'>#20</a> 0x08354911 in zend_objects_destroy_object ()
<a href='/21'>#21</a> 0x08357705 in zend_objects_store_call_destructors ()
<a href='/22'>#22</a> 0x08330be8 in shutdown_destructors ()
<a href='/23'>#23</a> 0x0833cd31 in zend_call_destructors ()
<a href='/24'>#24</a> 0x082f9e91 in php_request_shutdown ()
<a href='/25'>#25</a> 0x083a27cc in main ()
(gdb) 
@robocoder commented on December 3rd 2011 Contributor

Also segfaulting in Cookie.test.php. (The backtrace is uglier...looks like the stack is corrupted.)

@mattab commented on December 3rd 2011 Member

interesting, it is segfaulting during shutdown? could it be session related? do you have more info because this is not telling us where the but is unfortunately... ;) do you think it can be fixed?

@robocoder commented on December 3rd 2011 Contributor

(In [5520]) refs #2735, refs #2812

@robocoder commented on December 3rd 2011 Contributor

I narrowed it down to the test_infiniteRecursion. I guess we trigger an old php bug here. (no seg fault in 5.2 or later versions that I have).

@robocoder commented on December 4th 2011 Contributor

In tests/core/DataTable.tst.php's test_serializeWithInfiniteRecursion(), the seg fault happens even if I comment out the $table->getSerialized().

@mattab commented on December 7th 2011 Member

In tests/core/DataTable.tst.php's test_serializeWithInfiniteRecursion(), the seg fault happens even if I comment out the $table->getSerialized().

so the bug is in addRowFromArray ? Very strange... ! I have not yet setup 5.4 so cant debug now, but certainly interesting, might be a bug in PHP?

@robocoder commented on December 7th 2011 Contributor

Yes, bug happens after calling addRowFromArray using php 5.1.x. Works fine in 5.4.

@mattab commented on December 12th 2011 Member

Marking as wont fix.

In the segmentation fault faq we recommend to ugprade PHP to latest version, which covers this issue.

This Issue was closed on December 12th 2011
Powered by GitHub Issue Mirror