If build options break the plugin, I would rather put my money in a bug in the plugin (relying on undefined behavior, or at best, implementation-defined behavior) like memory corruption or something like this, that some protective build flags prevent from happening.

I'd suggest trying to run the plugin under i.e. Valgrind, and/or with some address sanitizer to see if they can't find some problems. I might try that later today, but I'm not sure I'd know how to reproduce at least the steps if not the behavior.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.