<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Dereferenced NULL pointer in StyleResolver"
href="https://bugs.webkit.org/show_bug.cgi?id=160823#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Dereferenced NULL pointer in StyleResolver"
href="https://bugs.webkit.org/show_bug.cgi?id=160823">bug 160823</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>(In reply to <a href="show_bug.cgi?id=160823#c2">comment #2</a>)
<span class="quote">> I don't understand how fixing a nullptr dereference can be no change in
> behavior? Dereferencing a nullptr will crash the program, so removing it
> would fix the crash and therefore be testable. Is that not the case here
> somehow?</span >
Dereferencing a null pointer and then passing the resulting reference does not necessarily crash the program; as you know under the hood references are implemented almost the same way that pointers are.
But Jonathan is using some kind of "undefined behavior testing mode" for clang, and so he was able to detect that the value is null. The rest of us are using clang in its normal compilation mode and like all the other compilers it just passes null to the function, which ignores the passed-in reference.</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>