[LLVMbugs] [Bug 21097] New: r600: segfault with nine d3d9 state tracker when compiled with clang

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Sep 30 04:35:53 PDT 2014


            Bug ID: 21097
           Summary: r600: segfault with nine d3d9 state tracker when
                    compiled with clang
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: haagch+llvm at frickel.club
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 13100
  --> http://llvm.org/bugs/attachment.cgi?id=13100&action=edit
full backtrace from debug build

So... I'm using a PITCAIRN HD 7970M and tried this d3d9 state tracker:
https://wiki.ixit.cz/d3d9 with the dri3 branches.

llvm is from a recent trunk build (218578) and so is clang.

When llvm is compiled with clang rendering something with d3d9 causes a
segfault in llvm.
When llvm is compiled with gcc 4.9.1 it works and does not segfault.

Interestingly there are different crashes with a release build and with a debug
build of llvm.

With a release build:

#0  0x7a0df883 in unsigned int
llvm::GraphTraits<llvm::BasicBlock*>::NodeType*, unsigned int) () from
#1  0x00002228 in ?? ()
#2  0x7cedd998 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

With a debug build: see attachment.

I do not know if this is a problem in clang or llvm. I'll just leave this here
in case someone knows what's going on.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140930/686a29ac/attachment.html>

More information about the llvm-bugs mailing list