summaryrefslogtreecommitdiffstats
path: root/lldb
Commit message (Collapse)AuthorAgeFilesLines
* <rdar://problem/11730263>Greg Clayton2013-03-289-158/+188
| | | | | | | | | | PC relative loads are missing disassembly comments when disassembled in a live process. This issue was because some sections, like __TEXT and __DATA in libobjc.A.dylib, were being moved when they were put into the dyld shared cache. This could also affect any other system that slides sections individually. The solution is to keep track of wether the bytes we will disassemble are from an executable file (file address), or from a live process (load address). We now do the right thing based off of this input in all cases. llvm-svn: 178315
* Making the buildbot happy again after changes to the default formatter for ↵Enrico Granata2013-03-283-5/+7
| | | | | | char[] llvm-svn: 178295
* <rdar://problem/12410225>Enrico Granata2013-03-281-1/+1
| | | | | | | By default, omit the children for a char[] and just show the string contents Can be overridden by appropriate command-line flags llvm-svn: 178292
* Hardening the vector iterator synthetic child(ren) provider against ↵Enrico Granata2013-03-281-1/+3
| | | | | | item-not-in-cluster asserts llvm-svn: 178265
* Be sure to take the mutex when the destructor is called in case other ↵Greg Clayton2013-03-282-0/+6
| | | | | | threads are using these lists and those other threads have the mutex locked. llvm-svn: 178262
* <rdar://problem/13527167>Greg Clayton2013-03-281-0/+4
| | | | | | | | Partial fix for the above radar. Call ThreadList::Clear() in the ThreadList destructor so if any other threads currently have the thread list mutex, we won't destroy the list for them while they are using it. ThreadList::Clear() takes the mutex and clears the thread list contents. llvm-svn: 178257
* Introduces extended register sets whose availability can vary with the ↵Ashok Thirumurthi2013-03-285-20/+103
| | | | | | | | | | target processor. - Includes a stub for AVX support in the x86-64 register context and a failing test for register sets that are unavailable. Thanks to Greg Clayton for his review feedback. llvm-svn: 178252
* Fix makefile build by linking needed library 'irreader'Daniel Malea2013-03-281-1/+1
| | | | llvm-svn: 178251
* Fix the Linux build issues introduced by r178191.Ashok Thirumurthi2013-03-288-45/+50
| | | | | | | | | - All Linux logging channels now use a single global instance of lldb_private::Log, to handle the case of logging during process tear down. - Also removed a single use of LogSP in FreeBSD and fixed a typo in a comment while reading through ProcessKDPLog. Reviewed by Daniel Malea. llvm-svn: 178242
* Debugserver fix for launching iOS apps who are named "com.apple.something"Jason Molenda2013-03-281-2/+16
| | | | | | | | - the ".app" would be treated as the app bundle final characters and the SpringBoard launch would fail. <rdar://problem/13258935> llvm-svn: 178209
* <rdar://problem/13412986>Enrico Granata2013-03-281-0/+3
| | | | | | | Holding the Python lock while we call the Python C API to post-process objects returned from the OS plugins This should avoid issues where some Python objects get invalidated while we are in the middle of processing them and we end up with an invalid Python state and a crash llvm-svn: 178206
* Protect against the case where the current inlined depth is wrong, and leads ↵Jim Ingham2013-03-282-30/+58
| | | | | | | | | | us to think we can't even get the frame at index 0. We should ALWAYS be able to get that. <rdar://problem/13497571> llvm-svn: 178205
* Use the error from ValidatePlan.Jim Ingham2013-03-281-1/+1
| | | | llvm-svn: 178204
* The other half of the checkin to produce better error messages when the ↵Jim Ingham2013-03-281-0/+1
| | | | | | ThreadPlanCallFunction isn't valid. llvm-svn: 178203
* RunThreadPlan should make sure the plan passed in is valid before running it.Jim Ingham2013-03-281-1/+7
| | | | | | <rdar://problem/13485541> llvm-svn: 178202
* Return a useful error message from ValidatePlan if the expression can't be ↵Jim Ingham2013-03-281-7/+23
| | | | | | made for some reason. llvm-svn: 178201
* This test case was not doing the right thing with libc++ being used and was ↵Enrico Granata2013-03-271-0/+3
| | | | | | generating spurious over-completion warning flags llvm-svn: 178192
* <rdar://problem/13521159>Greg Clayton2013-03-27155-1001/+1008
| | | | | | | | LLDB is crashing when logging is enabled from lldb-perf-clang. This has to do with the global destructor chain as the process and its threads are being torn down. All logging channels now make one and only one instance that is kept in a global pointer which is never freed. This guarantees that logging can correctly continue as the process tears itself down. llvm-svn: 178191
* Implementing the notion of externally-acquirable ScriptInterpreter lockEnrico Granata2013-03-275-1/+40
| | | | | | | | | | | | | | With this notion, if parties outside the ScriptInterpreter itself need to acquire a lock on script APIs, they can do so by a pattern like this: { auto lock = interpeter->AcquireInterpreterLock(); // do whatever you need to do... } // lock will automatically be released here This might be useful for classes that use the Python convenience objects (e.g. PythonDictionary) to ensure they keep the underlying interpreter in a safe and controlled condition while they call through the C API functions Of course, the ScriptInterpreter still manages its internal locking correctly when necessary :-) llvm-svn: 178189
* test commitAshok Thirumurthi2013-03-271-1/+1
| | | | | | - modified a comment llvm-svn: 178178
* <rdar://problem/13327940>Greg Clayton2013-03-271-2/+2
| | | | | | Cleaned up some paths. llvm-svn: 178177
* Added a source file needed for clang to compile in the lldb_perf_clang test.Greg Clayton2013-03-271-0/+24
| | | | llvm-svn: 178176
* <rdar://problem/13327940>Greg Clayton2013-03-271-12/+94
| | | | | | Enhance automated testing to include evaluating function calls. llvm-svn: 178175
* Fix a typo in help string.Jim Ingham2013-03-271-1/+1
| | | | llvm-svn: 178154
* Fixed a problem where inline assembly errors causedSean Callanan2013-03-271-1/+20
| | | | | | | | LLDB to crash. <rdar://problem/13497915> llvm-svn: 178115
* Don't use a "uintptr_t" for the metadata key, use a "void *". This removes ↵Greg Clayton2013-03-2712-73/+101
| | | | | | all of the casts that were being used and cleans the code up a bit. Also added the ability to dump the metadata. llvm-svn: 178113
* Prune more stuff out of the build and source folders after building clang.Greg Clayton2013-03-271-1/+3
| | | | llvm-svn: 178112
* Cleaned up how LLDB.framework was being linked to and also how the target ↵Greg Clayton2013-03-261-6/+38
| | | | | | dependencies. llvm-svn: 178085
* <rdar://problem/13339196>Enrico Granata2013-03-261-1/+5
| | | | | | | The algorithm to access an item in a __NSArrayM was not reacting properly to deletions The fix is to use a smarter formula that accounts for items shifting and the resulting notion of offsets in the table llvm-svn: 178076
* <rdar://problem/13246939>Enrico Granata2013-03-261-1/+1
| | | | | | Make format uint64_t[] actually work as designed llvm-svn: 178072
* Add a way to dump a ClangASTType to stdout for debugging purposes.Greg Clayton2013-03-262-0/+10
| | | | llvm-svn: 178071
* Trim the output build folder a bit to it isn't so large.Greg Clayton2013-03-261-1/+6
| | | | llvm-svn: 178070
* A few more tweaks to the python perf tests. Now there is a MemoryMeasurement.Greg Clayton2013-03-261-19/+60
| | | | llvm-svn: 178069
* Clean up logging a bit to not log when a command pipe is opened when “lldb ↵Greg Clayton2013-03-261-1/+1
| | | | | | object” logging is on. llvm-svn: 178068
* Data formatters cleanup:Enrico Granata2013-03-264-10/+9
| | | | | | | | | | - Making an error message more consistent - Ensuring the element size is not zero before using it in a modulus - Properly using target settings to cap the std::list element count - Removing spurious element size calculations that were unused - Removing spurious capping in std::map llvm-svn: 178057
* Don't crash when we have an element size of zero.Greg Clayton2013-03-261-10/+14
| | | | llvm-svn: 178056
* That wasn't a typo, if the short letter option is from a non-obvious source, ↵Jim Ingham2013-03-261-1/+1
| | | | | | I capitolize it in the help as an aid to memory. llvm-svn: 178052
* Our commands that end up displaying a ValueObject as part of their workflow ↵Enrico Granata2013-03-267-64/+45
| | | | | | | | | | | use OptionGroupValueObjectDisplay as their currency for deciding the final representation ValueObjects themselves use DumpValueObjectOptions as the currency for the same purpose The code to convert between these two units was replicated (to varying degrees of correctness) in several spots in the code This checkin provides one and only one (and hopefully correct :-) entry point for this conversion llvm-svn: 178044
* Change the stepping test to output "total time" for the step as well.Jim Ingham2013-03-262-12/+18
| | | | llvm-svn: 178043
* Fixed a typo.Sean Callanan2013-03-261-1/+1
| | | | llvm-svn: 178039
* Remove FunctionProfiler and ProfileObjectiveC action classes as they are not ↵Greg Clayton2013-03-265-849/+0
| | | | | | used. llvm-svn: 178035
* <rdar://problem/13502196>Greg Clayton2013-03-261-1/+12
| | | | | | We have the tag when figuring out the fully qualified name, append a suitable name for other types of tags when no name is available. llvm-svn: 177966
* <rdar://problem/13502196> Greg Clayton2013-03-262-2/+14
| | | | | | Functions in "(anonymous namespace)" was causing LLDB to crash when trying to complete a type and it would also cause functions arguments to appear in wrong place in frame display when showing function arguments. llvm-svn: 177965
* Make the stepping perf test case actually work.Jim Ingham2013-03-263-39/+308
| | | | llvm-svn: 177964
* <rdar://problem/13221060>Enrico Granata2013-03-261-0/+15
| | | | | | | | | | | | | | | | | | | Make register read and write accept $<regname> as valid. This allows: (lldb) reg read rbx rbx = 0x0000000000000000 (lldb) reg read $rbx rbx = 0x0000000000000000 (lldb) reg write $rbx 1 (lldb) reg read $rbx rbx = 0x0000000000000001 to function correctly It is not done at the RegisterContext level because we should keep the internal API clean of this user-friendly behavior and name registers appropriately. If this ends up being needed in more places we can reconsider. llvm-svn: 177961
* Checking that the wrong syntax does not give a correct summary after ↵Enrico Granata2013-03-261-0/+6
| | | | | | clearing the error messages here llvm-svn: 177949
* Modified patch from Prabhat Verma to enable loading core files through the ↵Greg Clayton2013-03-253-0/+43
| | | | | | SBTarget API. llvm-svn: 177932
* Fix the buildbot so a LLDB test doesn't fail looking for "<invalid usage of ↵Greg Clayton2013-03-251-6/+0
| | | | | | pointer value as object>". llvm-svn: 177926
* <rdar://problem/13498879> Greg Clayton2013-03-251-9/+2
| | | | | | C String summary is emitting "<invalid usage of pointer value as object>" for bad pointers. Now it doesn't emit anything. llvm-svn: 177913
* <rdar://problem/13498504>Han Ming Ong2013-03-252-11/+36
| | | | | | Don't hard code vm page size in profiling code llvm-svn: 177907
OpenPOWER on IntegriCloud