KWSys: Avoid undefined behavior in Process crash tests
Clang is smart enough to recognize that "*(int*)0=0" invokes undefined behavior, warns, and produces an "undefined instruction". The message in commit "Avoid Clang optimizer bug in testProcess-[45]" (2010-07-02) is incorrect; this is not a Clang bug. It really is undefined behavior. Use "*(int*)1=0" to produce a crash instead.
Loading
Please register or sign in to comment