You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Built ChakraCore with the hextype enabled version of clang from this repo on Ubuntu 16.04 LTS. I actually suspect that this could be a problem with Chakra's build makefiles, but I'd like help diagnosing what is going wrong.
Build succeeds, on attempting to run anything there is a fatal dllopen error.
This looks like some symbol that should have been compiled in when I included -fsanitize=hextype. Any ideas? I'm digging around trying to find a missing -fsanitize line at the moment. I'd be very happy to get any advice. I guess I'll attempt building the library statically and report back.
The text was updated successfully, but these errors were encountered:
Building the library with --static fixes the issue. I can also confirm hextype will catch some type confusions when compiled into the executable ch (though not in JIT compiled code since it lacks instrumentation) when it's compiled with ChakraCore embedded statically.
Pretty neat! Have you experienced issues using hextype sanitization in dynamic libraries? Is this maybe something smart people just know to avoid?
Built ChakraCore with the hextype enabled version of clang from this repo on Ubuntu 16.04 LTS. I actually suspect that this could be a problem with Chakra's build makefiles, but I'd like help diagnosing what is going wrong.
Build succeeds, on attempting to run anything there is a fatal dllopen error.
This looks like some symbol that should have been compiled in when I included -fsanitize=hextype. Any ideas? I'm digging around trying to find a missing -fsanitize line at the moment. I'd be very happy to get any advice. I guess I'll attempt building the library statically and report back.
The text was updated successfully, but these errors were encountered: