Open Quuxplusone opened 12 years ago
Bugzilla Link | PR11844 |
Status | NEW |
Importance | P enhancement |
Reported by | mandy (mandys.inbox@gmail.com) |
Reported on | 2012-01-24 05:08:23 -0800 |
Last modified on | 2019-05-24 14:20:55 -0700 |
Version | unspecified |
Hardware | Macintosh MacOS X |
CC | anton@korobeynikov.info, flash@pobox.com, jryans@gmail.com, kremenek@apple.com, llvm-bugs@lists.llvm.org, mandys.inbox@gmail.com |
Fixed by commit(s) | |
Attachments | |
Blocks | |
Blocked by | |
See also |
Have you tried to "Please file a bug at http://bugreport.apple.com with this
warning message and
any useful information you can provide." as you were suggested?
This is part of the limitation of scan-build. It doesn't know what compiler
Xcode intended to use for compilation, so it just defaults to gcc (which
doesn't recognize the arguments -fdiagnostics-print-source-range-info, and so
forth).
Beyond the link you cited, there is no really good way to fix this in scan-
build without doing REAL interposition of the build (e.g., intercept exec's of
the compiler and run the analyzer on the side) instead of the poor man's
interposition we are doing now by overriding the compiler used by xcodebuild.
Unfortunately, there are no resources currently allocated to that effort.
You're best bet for Xcode integration (right now) is to use the set-xcode-
analyzer script:
http://clang-analyzer.llvm.org/xcode.html
and run the analyzer directly within Xcode or from the command line using
xcodebuild.
Retitling to reflect the broader fix that is need, which is essentially a reimplementation of scan-build.