<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 --- - Fission interacts poorly with crash reporting"
   href="http://llvm.org/bugs/show_bug.cgi?id=16928">16928</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Fission interacts poorly with crash reporting
          </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>All
          </td>
        </tr>

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

        <tr>
          <th>Keywords</th>
          <td>googler
          </td>
        </tr>

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

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

        <tr>
          <th>Component</th>
          <td>Driver
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedclangbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>dblaikie@gmail.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>echristo@gmail.com, llvmbugs@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Filing off the cuff (for me or Eric or anyone to look at more closely at some
point) - it looks, at first glance, like fission (-gsplit-dwarf) is interacting
poorly with Clang's crash reporting functionality.

For example, I got a crash report with the following .sh file:

/mnt/fast/dev/llvm/build/clang/debug/bin/clang-3.3 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name
opt.cpp -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -fmath-errno
-masm-verbose -mconstructor-aliases -munwind-tables -target-cpu x86-64 -g -g
-backend-option -split-dwarf=Enable -D "_DEBUG" -D "_GNU_SOURCE" -D
"__STDC_CONSTANT_MACROS" -D "__STDC_FORMAT_MACROS" -D "__STDC_LIMIT_MACROS" -D
"opt_EXPORTS" -Wall -W -Wno-unused-parameter -Wwrite-strings
-Wmissing-field-initializers -Wno-long-long -Wcovered-switch-default
-Wnon-virtual-dtor -Werror -pedantic -std=c++11 -fconst-strings
-fdeprecated-macro -ferror-limit 19 -fmessage-length 0
-fvisibility-inlines-hidden -mstackrealign -fno-rtti -fobjc-runtime=gcc
-fobjc-default-synthesize-properties -fdiagnostics-show-option
-fcolor-diagnostics -vectorize-slp -x c++
/usr/local/google/home/blaikie/dev/llvm/src/tools/opt/opt.cpp -split-dwarf-file
opt-65300c.cpp.dwo


Notice that the '.cpp' file name has not been modified to refer to the crash
report post-processed file, but the split-dwarf file name seems to have been
changed.

Hand modifying the script/command to refer to opt-65300c.cpp produces the
expected reproducible crash.</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>