Skip to content

Conversation

@casperisfine
Copy link
Contributor

Ref: msgpack/msgpack-ruby#314 (comment)

We experienced some weird segfault in msgpack_buffer_mark we couldn't explain.

Until we noticed that the object being marked wasn't a MessagePack::Buffer but a StackFrames::Buffer.

Both msgpack and stackframes were using the same symbol name to declare their respective buffer type, and the msgpack one was registered first.

This is the counterpart of msgpack/msgpack-ruby#317 and generally speaking all gems should compile with -fvisibility=hidden.

Ref: msgpack/msgpack-ruby#314 (comment)

We experienced some weird segfault in `msgpack_buffer_mark` we couldn't explain.

Until we noticed that the object being marked wasn't a `MessagePack::Buffer` but
a `StackFrames::Buffer`.

Both `msgpack` and `stackframes` were using the same symbol name to declare
their respective buffer type, and the msgpack one was registered first.

This is the counterpart of msgpack/msgpack-ruby#317
and generally speaking all gems should compile with `-fvisibility=hidden`.
@casperisfine casperisfine merged commit 34fea15 into main Mar 1, 2023
@shopify-shipit shopify-shipit bot temporarily deployed to rubygems March 1, 2023 17:50 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants