llvm-svn: 189231

llvm-svn: 189192

llvm-svn: 189191

llvm-svn: 189163

SBProcess::ReadMemory - it will fail for anything with the high bit set.

llvm-svn: 189154

llvm-svn: 189107

llvm-svn: 189082

live beyont parsing.  This is important because
all the ClangASTImporter::Minions for a parser's
ASTContext are cleared when ClangExpressionDeclMap
is deleted.

This resolves many hard-to-reproduce crashes,
especially ones involving breakpoint conditions.

<rdar://problem/14775391>

llvm-svn: 189080

llvm-svn: 189077

methods in the ABIs.  Specify the register numbering of the UnwindPlan
we're creating and use those only register numbers.

llvm-svn: 189074

16-byte alignment of stack frames.

llvm-svn: 189073

llvm-svn: 189066

llvm-svn: 189062

llvm-svn: 189061

llvm-svn: 189058

llvm-svn: 188973

llvm-svn: 188972

llvm-svn: 188955

llvm-svn: 188954

llvm-svn: 188952

llvm-svn: 188912

llvm-svn: 188907

llvm-svn: 188892

llvm-svn: 188809

Patch from Abid, Hafiz.

llvm-svn: 188801

Patch from Abid, Hafiz.

llvm-svn: 188776

instead of pointing to a page with two links on it.

llvm-svn: 188706

llvm-svn: 188704

llvm-svn: 188703

This means that "register read stmm0 --format f" actually works now.

This is a little messy but LLDB assumes 'long double' is portable, when it is not.

llvm-svn: 188698

we've read the ObjectFile's Symtab before we change the
File addresses in the Sections.

llvm-svn: 188604

llvm-svn: 188570

address.

When loading a dSYM, and the file addresses of the dSYM Sections are
different than the executable binary Sections' file addresses, the
debug info won't be remapped to the actual load addresses correctly.
This only happens with binaries on the in-memory shared cache binaries
where their File addresses have been set to their actual load address
(outside an offset value) whereas the original executable and dSYM
have 0-based File addresses.

I think this patch will not be activated for other cases -- this is
the only case we know of where the dSYM and the executable's File
addresses differ -- but if this causes other problems we can restrict
it more carefully.

<rdar://problem/12335086> 

llvm-svn: 188532

where the executable has been slid.  This detects the regression fixed in
r188289.

llvm-svn: 188443

Improve the documentation for the new target.memory-module-load-level setting, and also return an error when there is no nlist data when appropriate.

llvm-svn: 188317

way of making LLVM not rely on terminfo.

llvm-svn: 188305

When adding a dSYM file, don't remove all sections for the Module's object file if the symbol vendor used the same object file.

llvm-svn: 188289

Patch by Abid, Hafiz

llvm-svn: 188270

a bunch of semicolons where the IndirectFieldDecls
were.  These IndirectFieldDecls should have been
implicit.

<rdar://problem/14628784>

llvm-svn: 188247

LLDB needs in memory module load level settings to control how much information is read from memory when loading in memory modules. This change adds a new setting:

(lldb) settings set target.memory-module-load-level [minimal|partial|complete]

minimal will load only sections (no symbols, or function bounds via function starts or EH frame)
partial will load sections + bounds
complete will load sections + bounds + symbols

llvm-svn: 188246