llvm-svn: 123049

was being searched and sorted using a shared pointer as the value which means
the pointer value was what was being searched for. This means that anytime
you did a stack backtrace, the collection of FuncUnwinders doubled and then
the array or shared pointer got sorted (by pointer value), so you had an ever
increasing collection of shared pointer where a match was never found. This
means we had a ton of duplicates in this table and would cause issues after
one had been debugging for a long time.

llvm-svn: 123045

by any means, but something to stress test our unwinder with 260,000+ frames
on a standard darwin thread.

llvm-svn: 123037

command to do the disassembly.  Instead, use the Python API.

llvm-svn: 123029

llvm-svn: 123002

subclasses will automatically be able to take advantage of caching. The
cache line size is set to 512 by default.

This greatly speeds up stack backtraces on MacOSX when using the 
ProcessGDBRemote process plug-in since only about 6300 packets per second
can be sent.

Initial speedups show:

Prior to caching: 10,000 stack frames took 5.2 seconds
After caching: 10,000 stack frames in 240 ms!

About a 20x speedup!

llvm-svn: 122996

cache even when a valid process exists. Previously, Target::ReadMemory would
read from the process if there was a valid one and then fallback to the
object file cache.

llvm-svn: 122989

llvm-svn: 122985

Also, call GetProcess instead of CalculateProcess as the latter is morally part
of the ExecutionContextScope API.

llvm-svn: 122984

try and build this and let me know how it goes?

llvm-svn: 122981

an issue with the way the UnwindLLDB was handing out RegisterContexts: it
was making shared pointers to register contexts and then handing out just
the pointers (which would get put into shared pointers in the thread and
stack frame classes) and cause double free issues. MallocScribble helped to
find these issues after I did some other cleanup. To help avoid any
RegisterContext issue in the future, all code that deals with them now
returns shared pointers to the register contexts so we don't end up with
multiple deletions. Also now that the RegisterContext class doesn't require
a stack frame, we patched a memory leak where a StackFrame object was being
created and leaked.

Made the RegisterContext class not have a pointer to a StackFrame object as
one register context class can be used for N inlined stack frames so there is
not a 1 - 1 mapping. Updates the ExecutionContextScope part of the 
RegisterContext class to never return a stack frame to indicate this when it
is asked to recreate the execution context. Now register contexts point to the
concrete frame using a concrete frame index. Concrete frames are all of the
frames that are actually formed on the stack of a thread. These concrete frames
can be turned into one or more user visible frames due to inlining. Each 
inlined stack frame has the exact same register context (shared via shared
pointers) as any parent inlined stack frames all the way up to the concrete 
frame itself.

So now the stack frames and the register contexts should behave much better.

llvm-svn: 122976

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