__debugInfo fails after unserialize()

[assertchris]

SerializableClosure::serialize() does not account for SerializerInterface $serializer = null, in the constructor. If this parameter isn't provided then the default serializer, which the constructor creates, is not created during SerializableClosure::unserialize().

PHP Fatal error:  Call to a member function getData() on null in /[redacted]/vendor/jeremeamia/SuperClosure/src/SerializableClosure.php on line 164
PHP Stack trace:
PHP   1. {main}() /[redacted]/debug.php:0
PHP   2. print_r() /[redacted]/debug.php:20
PHP   3. SuperClosure\SerializableClosure->__debugInfo() /[redacted]/debug.php:20

Fatal error: Call to a member function getData() on null in /[redacted]/vendor/jeremeamia/SuperClosure/src/SerializableClosure.php on line 164

Call Stack:
    0.0003     230504   1. {main}() /[redacted]/debug.php:0
    0.0308    3387808   2. print_r() /[redacted]/debug.php:20
    0.0308    3388216   3. SuperClosure\SerializableClosure->__debugInfo() /[redacted]/debug.php:20

[travisulrich]

I also ran across this issue yesterday. var_dump works successfully on the serialized object, but print_r causes the error @assertchris mentioned above.

[Anahkiasen]

Small reproducible test case:

$closure = new SuperClosure\SerializableClosure(function() {});
var_dump($closure); // Works

$closure = unserialize(serialize($closure));
var_dump($closure); // Crashes

[GrahamCampbell]

@Anahkiasen Surely $closure = unserialize(serialize($closure))->getClosure(); is the correct usage here?

[jeremeamia]

Thanks for the bug report and repro code.

[Anahkiasen]

@GrahamCampbell Not that I know of no, the SerializableClosure wraps the closure and is still callable, it's more like a decorator