Patch by Robert Matusewicz

llvm-svn: 206711

When compiling on Linux with GCC 4.8, compilation would fail due to the use of
the offsetof macro.  This is a standard macro, defined in stddef.h.  Include
this header to ensure that offsetof is declared.

llvm-svn: 206702

using preprocessor constants for printf() format
specifications.

llvm-svn: 206679

llvm-svn: 206620

llvm-svn: 206619

Follow-up patch coming to address test failures exposed by this change.

llvm-svn: 206618

llvm-svn: 206524

After updating to Xcode.5.1.1 LLDB framework stopped to support partial (only for STDIN) pseudo terminal usage in the debugging process.
Here is the fix resolving this issue.

Patch from Alexey Ushakov.

llvm-svn: 206476

Sponsored by: DARPA, AFRL
Differential Revision: http://reviews.llvm.org/D3401

llvm-svn: 206469

llvm-svn: 206468

It will shortly be need by FreeBSD elf core support on all hosts.

llvm-svn: 206466

llvm-svn: 206351

interrupt.  Do both of those.

llvm-svn: 206350

llvm-svn: 206319

llvm-svn: 206278

Make LLDB builds against the current LLVM sources (modification on createMCDisassembler introduced by r206241)

llvm-svn: 206277

I saw a complain about this code on the LLVM channel. It looks wrong to me
as has_tag is a boolean. I am committing it as obvious.

llvm-svn: 206270

when it is reading the kext table, in case we're reading out of a core file with
corrupt contents in this region.
<rdar://problem/16601915> 

llvm-svn: 206233

Patch from Michael Tao.

llvm-svn: 206213

llvm-svn: 206212

Patch from Vyacheslav Karpukhin.

llvm-svn: 206040

The "unexpected value" message only matters to me, but is bound to make the experience more confusing for people when some uninitialized memory looks like an NSNumber and then can't be formatted properly, and that error comes out in the UI

Just drop the error message entirely - nobody but me cares

llvm-svn: 205978

Enable data formatters to see-through pointers/references to typedefs

For instance, if Foo is a typedef to Bar, and there is a formatter for any/all of Bar*, Bar&, Bar&&, then Foo*, Foo&, and Foo&& should pick these up if Foo-specific formatters don't exist

llvm-svn: 205939

When trying to extract the type info for an r-value reference type, dont' cast to an l-value reference type

llvm-svn: 205932

Set the correct FormatManager revision before starting to figure out the new formatters
This can avoid entering some corner cases where as part of figuring out formatters we try to figure out dynamic types, and in turn that causes us to go back in trying to fetch new formatters - it is not only a futile exercise, it's also prone to endless recursion

This would only cause a behavior change if getting this chain started would eventually cause something to run and alter the formatters, a very unlikely if at all possible sequence of events

llvm-svn: 205928

TIDs are conventionally shown as decimal values on FreeBSD and Linux.
Thus, use the ${thread.id%tid} format string to display the thread ID,
instead of a fixed hex format.

llvm.org/pr19380

llvm-svn: 205912

Calling mutex_lock from one thread and then mutex_unlock from another is
not permitted.  Replace the awkward mutex usage with a mutex and
condition variable.

llvm.org/pr18061                                                            

llvm-svn: 205900

dbg_value intrinsics appropriately.

<rdar://problem/16504649>

llvm-svn: 205825

Fixed module spec matching to not try to compare the platform path if there isn't one in the ModuleSpec that is asked if it matches.

<rdar://problem/16558568>

llvm-svn: 205816

but by the time we go to halt, it has already stopped by hitting the 
function end breakpoint.  That wasn't being shown to the threads so the
Function call thread plan didn't know its job was done.

<rdar://problem/16515785>

llvm-svn: 205803

llvm-svn: 205790

Also, the stride is now a pointer so one can avoid passing it if it's not required

llvm-svn: 205782

error: declaration of constexpr static data member 'spec' requires an
initializer

llvm-svn: 205776

Issue reported by Matthew Gardiner.  Further work is necessary to
synchronize LLDB's DWARF classes with the derivatives now in LLVM.

llvm-svn: 205771

llvm-svn: 205770

llvm-svn: 205769

SBTarget::AddModule(const char *path,
                    const char *triple,
                    const char *uuid_cstr,
                    const char *symfile);
                    
If "symfile" was filled in, it would cause us to not correctly add the module. Same goes for:

SBTarget::AddModule(SBModuleSpec ...)

Where you filled in the symfile.

<rdar://problem/16529799>

llvm-svn: 205750

<rdar://problem/16535437>

llvm-svn: 205740

llvm-svn: 205739

Disable JITLoaderGDB on "vendor == apple" for now due to performance slowdowns for every first run process as a global name lookup in all shared libraries if performed.

<rdar://problem/16542894>

llvm-svn: 205734