<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Dec 5, 2011, at 5:08 PM, Anna Zaks wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Thanks for the feedback. I think the best solution would be to mention the possible redundant check in the diagnostic. Please, file a bug report!<br></span></blockquote></div><br><div>This is a place where taint analysis would also be potentially useful. If the pointer value is influenced by a tainted source, it probably should be treated as being a more severe candidate for a real null dereference, even in the cases where we can't fully prove that a null dereference occurred.</div></body></html>