Description:
------------
When user class extends internal class with get_debug_info object handler set and defined userland __debugInfo() method, that method totally ignored.


As a workaround, Z_OBJDEBUG macro may be changed to looks like

    #define Z_OBJDEBUG(zval,tmp)		(Z_OBJCE(zval)->__debugInfo?std_object_handlers.get_debug_info(&(zval),&tmp):(Z_OBJ_HANDLER((zval),get_debug_info)?Z_OBJ_HANDLER((zval),get_debug_info)(&(zval),&tmp):(tmp=0,Z_OBJ_HANDLER((zval),get_properties)?Z_OBJPROP(zval):NULL)))

From Bob Weinand notes:

Then comes a question about parent::__debugInfo() in userland __debugInfo() 
comes: should it be accessible? Should it return what get_debug_info returns? Or should get_debug_info moved to ce->__debugInfo (internally too)? BC?


Test script:
---------------
class CustomSplStorage extends SplObjectStorage {
    public function __debugInfo()
    {
        return ['this is' => 'annoying'];
    }
}

var_dump(new CustomSplStorage());
debug_zval_dump(new CustomSplStorage());

Expected result:
----------------
object(CustomSplStorage)#1 (1) {
  ["this is"]=>
  string(8) "annoying"
}
object(CustomSplStorage)#1 (1) refcount(1){
  ["storage":"SplObjectStorage":private]=>
  ["this is"]=>
  string(8) "annoying" refcount(2)
}


Actual result:
--------------
object(CustomSplStorage)#1 (1) {
  ["storage":"SplObjectStorage":private]=>
  array(0) {
  }
}
object(CustomSplStorage)#1 (1) refcount(1){
  ["storage":"SplObjectStorage":private]=>
  array(0) refcount(1){
  }
}