<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Member call on NULL pointer in JavaScriptCore/dfg/DFGAbstractInterpretterInlines.h"
href="https://bugs.webkit.org/show_bug.cgi?id=160870#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Member call on NULL pointer in JavaScriptCore/dfg/DFGAbstractInterpretterInlines.h"
href="https://bugs.webkit.org/show_bug.cgi?id=160870">bug 160870</a>
from <span class="vcard"><a class="email" href="mailto:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>Jonathan has been compiling WebKit with clang's UndefinedBehaviorSanitizer <<a href="http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html">http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html</a>>. When compiled like this, code will trap if it makes a non-static function member call with a nullptr for the this pointer.
I think of it as a way to add additional assertions.
When Jonathan is saying that a test "exhibits the bug", he means that when compiled that way, that test hit the trap.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>