[Bug 15407] New: LLDB segmentation fault running TestDisassemble_VST1_64 in LLVMCreateDisasmCPU()

Bug ID 15407
Summary LLDB segmentation fault running TestDisassemble_VST1_64 in LLVMCreateDisasmCPU()
Product lldb
Version unspecified
Hardware PC
OS Linux
Status NEW
Severity enhancement
Priority P
Component All Bugs
Assignee lldb-dev@cs.uiuc.edu
Reporter daniel.malea@intel.com
Classification Unclassified

This issue is about an IRC crash report about LLDB (r176306). It seems to be
happening during the initialization of the LLVM disassembler.

OS: Linux
Compiler: clang (176308)
Build system: cmake (release build)

Unable to reproduce locally with an older version of Clang (or GCC 4.6/4.7) but
the stack trace from the crash is:

(gdb) bt
#0  0x00007ffff39abb48 in LLVMCreateDisasmCPU () from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so
#1  0x00007ffff3114e58 in
DisassemblerLLVMC::DisassemblerLLVMC(lldb_private::ArchSpec const&) ()
   from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so
#2  0x00007ffff3114dd6 in
DisassemblerLLVMC::CreateInstance(lldb_private::ArchSpec const&) ()
   from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so
#3  0x00007ffff2fb1b07 in
lldb_private::Disassembler::FindPlugin(lldb_private::ArchSpec const&, char
const*) ()
   from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so
#4  0x00007ffff2fb279e in
lldb_private::Disassembler::DisassembleBytes(lldb_private::ArchSpec const&,
char const*, lldb_private::Address const&, void const*, unsigned long, unsigned
int) () from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so
#5  0x00007ffff2f2e5ed in lldb::SBTarget::GetInstructions(lldb::SBAddress, void
const*, unsigned long) ()
   from
/home/jey/code/llvm/build-lldb/lib/python2.7/site-packages/lldb/_lldb.so

Daniel Malea changed bug 15407

What Removed Added
Status NEW RESOLVED
Resolution WORKSFORME

Comment # 3 on bug 15407 from Daniel Malea

Unable to reproduce with LLDB trunk (debug or release builds) using either gcc
4.7 or clang-3.3 or clang (trunk)...

Closing unless someone can confirm this is indeed still an issue.