<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">In addition, the analyzer's plist output does support multi-file paths. So depending on how you consume the output this might be useful. Note, we change the format of the plist often and do not guarantee supporting it forever. However, there are python utilities in clang/utils/analyzer that can help you parse the output (CmpRuns.py); these are mainly used for testing now. <div><br></div><div>Anna.<br><div><div>On Jul 1, 2013, at 6:07 PM, Jordan Rose <<a href="mailto:jordan_rose@apple.com">jordan_rose@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>There's not currently a great way to do it. There's an internal option named "-analyzer-output" which accepts the value "text", but the display is currently broken in that path notes aren't attached to their associated warnings. This wouldn't be too hard to fix, but no one's gotten around to it yet.</div><div><br></div><div>You could cheat by preprocessing the source first and then analyzing<span class="Apple-converted-space"> </span><i>that</i>,<i> </i>but the resulting syntax-colored HTML file is usually<span class="Apple-converted-space"> </span><i>massive,</i> bogging down many browsers.</div><div><br></div><div>Basically, no one's put in the effort for this. ...patches welcome?</div><div><br></div><div>Sorry,</div><div>Jordan</div><div><br></div><br><div><div>On Jul 1, 2013, at 12:48 , Óscar Fuentes <<a href="mailto:ofv@wanadoo.es">ofv@wanadoo.es</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">A known limitation of the html output of scan-build is that it ignores<br>warnings whose paths spans more than one file [1]<br><br>Is there a way of obtaining the path associated to a warning when it<br>spans multiple files?<br><br>[1]<span class="Apple-converted-space"> </span><a href="http://llvm.org/bugs/show_bug.cgi?id=16489">http://llvm.org/bugs/show_bug.cgi?id=16489</a><br><br>_______________________________________________<br>cfe-dev mailing list<br><a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br></blockquote></div><br>_______________________________________________<br>cfe-dev mailing list<br><a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a></div></blockquote></div><br></div></body></html>