Segmentation fault when calling getKeys after getting a variable from Redis when the serializer is enabled.

[niekie]

When calling "getKeys" after a "get" call to fetch an item from the Redis database, a segmentation fault happens in the PHP process if the serializer is set to Redis::SERIALIZER_PHP.

The following 2 PHP interactive console sessions demonstrate the bug:

Interactive shell

php > $redis = new Redis;
php > $redis->connect('127.0.0.1', 6379);
php > print $redis -> get( 'hello' );
world
php > print_r( $redis -> getKeys( '*' ) );
Array
(
    [0] => hello
)

Interactive shell

php > $redis = new Redis;
php > $redis->connect('127.0.0.1', 6379);
php > $redis -> setOption( Redis::OPT_SERIALIZER, Redis::SERIALIZER_PHP );
php > print $redis -> get( 'hello' );
world
php > print_r( $redis -> getKeys( '*' ) );
Segmentation fault: 11

[michael-grunder]

Hey,

So I assume what you mean is that there is an issue when you get a key from Redis that is not serialized, but with Redis::SERIALIZER_PHP enabled, and then run keys.

I do not get a segfault when running that code, but my keys command returns this:

array(1) {
  [0] =>
  NULL
}

I also have the "hello" key in my database, so there does look to be something odd going on here. Could you do me a favor and send me the exact php version you're running?

Cheers!
Mike

[michael-grunder]

Hey there, can you try it now? I fixed a memory leak related to a serialization failure and while it didn't segfault for me, the weird behavior is now gone. I think it is related. :)

Cheers!
Mike

[niekie]

Hello Michael,

Thank you for your quick response! I am unable to reproduce the earlier behavior described with the newer version compiled from git, so your change seems to have resolved the issue.

Thanks again!

• Niek