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
This enables ubsan (undefined behavior sanitization) which means at runtime the program will check for undefined behavior. The -fsanitize-trap=undefined option is used when the sanitizer runtime is unavailable, and seems to result in "illegal instruction" errors rather than nice easy-to-debug panics (i.e. #9701).
I propose that Zig implement or include the ubsan runtime and by default have it print stack traces like a normal zig panic would do.
The text was updated successfully, but these errors were encountered:
Right now
zig cc
uses the following options.This enables ubsan (undefined behavior sanitization) which means at runtime the program will check for undefined behavior. The
-fsanitize-trap=undefined
option is used when the sanitizer runtime is unavailable, and seems to result in "illegal instruction" errors rather than nice easy-to-debug panics (i.e. #9701).I propose that Zig implement or include the ubsan runtime and by default have it print stack traces like a normal zig panic would do.
The text was updated successfully, but these errors were encountered: