Update lib/Makefile to use current LLVM and Clang components and add the
PluginUtility library to the build.

llvm-svn: 122975

In particular, we are looking to ignore the "#pragma mark" construct which GCC
warns about on platforms other than Darwin.  This cleans up diagnostic output
significantly.

llvm-svn: 122974

number string as found in the resources/LLDB-info.plist file.

llvm-svn: 122930

previously added ordinal number of the currently running test case.

llvm-svn: 122922

describing the ordinal number of the currently running test case.

llvm-svn: 122901

at debugserver-124.

llvm-svn: 122897

Fixed the display of complex numbers in lldb_private::DataExtractor::Dump(...)
and also fixed other edge display cases in lldb_private::ClangASTType::DumpTypeValue(...).

llvm-svn: 122895

llvm-svn: 122842

llvm-svn: 122841

llvm-svn: 122840

llvm-svn: 122839

llvm-svn: 122838

This code was a temporary workaround due to the lack of a dynamic loader plugin
for the Linux platform that has bit rotted over time.  Instead of replacing this
hack with another a proper plugin will be developed instead.

llvm-svn: 122837

Update ProcessLinux method signatures to be in line with LLDB's current API.

llvm-svn: 122836

Host::StopMonitoringChildProcess has been removed.  Provide a substitute.

llvm-svn: 122835

llvm-svn: 122834

were not being created in the proper way, meaning
results were getting lost.

llvm-svn: 122800

 

llvm-svn: 122797

llvm-svn: 122770

llvm-svn: 122767

And decorate the test cases as @expectedFailure.

llvm-svn: 122525

test case test_help_version().

llvm-svn: 122515

For the language check in GetObjectDescription, if we can't find a language runtime for the value we're looking at, BUT it IS at least a pointer, try the ObjCRuntime language.  That's currently the only language runtime that has an object description method anyway...

llvm-svn: 122465

"frame variable" requires that the process be running and paused or there aren't any frames...  So mark the  command properly as such.

llvm-svn: 122464

get the argument values of the call stacks when stopped on the breakpoint.

Radar has been filed for the expected failures:
test failure: ./dotest.py -v -w -t -p TestFrames (argument values are wrong)

llvm-svn: 122460

llvm-svn: 122450

and run the "process continue" command, use the SBProcess.Continue() API.

llvm-svn: 122434

NULL, instead of registering a NULL listener and to crash later.

llvm-svn: 122429

llvm-svn: 122428

0 mid-stack, stop backtracing.

SectionLoadList.cpp (ResolveLoadAddress): Don't assert on an
out-of-range address, just return an invalid Address object.
The unwinder may be passing in invalid addresses on the final
stack frame and the assert is a problem.

llvm-svn: 122386

llvm-svn: 122382

and waiting for two expected state changed events to arrive: "running" followed by
"stopped".

llvm-svn: 122380

llvm-svn: 122352

the process.  The custom thread started before this point is running in a loop
waiting for events to come.

llvm-svn: 122316

llvm-svn: 122308

llvm-svn: 122306

debugger and to exercise some event APIs.

llvm-svn: 122304

Remove an assertion that is causing crashes. We do need to find a way to reproduce when this assertion asserts, but we should crash our debug session because of it. For now we log to stderr in hope of tracking it down.

llvm-svn: 122290

scan the debugger output for program counter when it comes to the output of 'Up Stack' or 'Down Stack'
gud commands.  Remove the single quotes around the argument strings for "settings set frame-format"
and "settings set thread-format" commands to avoid the single quotes which were being emitted as part
of the debugger output.

llvm-svn: 122286

Provide a missing resolve_path argument in calls to FileSpec's
constructor for both Linux and FreeBSD code fragments.

llvm-svn: 122275