<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - checker doesn't work if there's a '-m' in the file path"
   href="http://llvm.org/bugs/show_bug.cgi?id=19191">19191</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>checker doesn't work if there's a '-m' in the file path
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>clang
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Static Analyzer
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>kremenek@apple.com
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>icculus@icculus.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvmbugs@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>(tested against checker-276)

If you have a "-m" somewhere in a source file's path, checker thinks it's a
compiler option due to a buggy regexp.

To reproduce:

- Put any project you build with scan-build into a directory with with a "-m"
in it (in our case, it was "/buildbot/slave/SDL/sdl-macosx-checker/src"). If
your build doesn't supply full path names, just add a file to the project
called file-m.c.

- Run "scan-build make" or whatnot to build the project. Files that are passed
to ccc-analyzer with a "-m" will compile correctly but never report bugs.

The bug appears to be here, in ccc-analyzer

  if ($Arg =~ /-m.*/) {
    push @CompileOpts,$Arg;
    next;
  }

There should probably be a '^' at the start of that regexp. I assume this is to
catch command line arguments like -msse2 or -m32, etc. Without that caret,
source files can get caught up in this test and don't get analyzed.

--ryan.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>