Actions
Bug #17552
closed[PATCH] Fix a NULL pointer crash in ObjectSpace.dump_all
Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin19]
Description
Patch: https://github.com/ruby/ruby/pull/4078
I wasn't able to reproduce the issue in isolation just yet, but I confirmed the patch fixes the issue for us.
What seem to happen in that some objects have an allocation_info
, but allocation_info->path == NULL
.
What is weird is that in 2.7.2, there was no NULL check for ->path
, it was directly passed to vfprintf
, which from what I understand would have generated "path": (null)
, which is invalid JSON.
So I suspect allocation_info { path = NULL }
wasn't possible on 2.7.2?
Either way I'd like to write a test case for this, but I'm still unable to find a way to create an object with a NULL path
.
Actions
Like0
Like0Like0Like0