- Dec 22, 2011
-
-
Johnny Chen authored
llvm-svn: 147172
-
Johnny Chen authored
With some minor modification from me. llvm-svn: 147160
-
Jim Ingham authored
Switch from GetReturnValue, which was hardly ever used, to GetReturnValueObject which is much more convenient. Return the "return value object" as a persistent variable if requested. llvm-svn: 147157
-
- Dec 21, 2011
-
-
Sean Callanan authored
parser has hitherto been an implementation waiting for a use. I have now tied the '-o' option for the expression command -- which indicates that the result is an Objective-C object and needs to be printed -- to the ExpressionParser, which communicates the desired type to Clang. Now, if the result of an expression is determined by an Objective-C method call for which there is no type information, that result is implicitly cast to id if and only if the -o option is passed to the expression command. (Otherwise if there is no explicit cast Clang will issue an error. This behavior is identical to what happened before r146756.) Also added a testcase for -o enabled and disabled. llvm-svn: 147099
-
Johnny Chen authored
llvm-svn: 147072
-
- Dec 20, 2011
-
-
Johnny Chen authored
llvm-svn: 146957
-
Johnny Chen authored
llvm-svn: 146956
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add a NULL check for SBValue.CreateValueFromExpression(). llvm-svn: 146954
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add a NULL check for SBTarget.AttachToProcessWithName() so it will not hang. llvm-svn: 146948
-
Johnny Chen authored
llvm-svn: 146935
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add NULL checks for SBStream APIs. llvm-svn: 146934
-
Johnny Chen authored
llvm-svn: 146924
-
Johnny Chen authored
llvm-svn: 146922
-
- Dec 19, 2011
-
-
Johnny Chen authored
llvm-svn: 146919
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add NULL checks for SBDebugger APIs. llvm-svn: 146917
-
Johnny Chen authored
llvm-svn: 146912
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add NULL checks for SBCommandReturnObject.AppendMessage(). llvm-svn: 146911
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add NULL checks for SBCommandInterpreter APIs. llvm-svn: 146909
-
Johnny Chen authored
rdar://problem/10577182 Audit lldb API impl for places where we need to perform a NULL check Add NULL checks for SBModule and SBSection APIs. llvm-svn: 146899
-
Sean Callanan authored
"id" from being found by the parser as an externally-defined type. Before, "id" would sometimes make it through if it was defined in a namespace, but this sometimes caused confusion, for example when it conflicted with std::locale::id. llvm-svn: 146891
-
Johnny Chen authored
llvm-svn: 146890
-
- Dec 17, 2011
-
-
Jim Ingham authored
llvm-svn: 146777
-
Johnny Chen authored
valobj.AddressOf() returns None when an address is expected in a SyntheticChildrenProvider Patch from Enrico Granata: The problem was that the frozen object created by the expression parser was a copy of the contents of the StgClosure, rather than a pointer to it. Thus, the expression parser was correctly computing the result of the arithmetic&cast operation along with its address, but only saving it in the live object. This meant that the frozen copy acted as an address-less variable, hence the problem. The fix attached to this email lets the expression parser store the "live address" in the frozen copy of the address when the object is built without a valid address of its own. Doing so, along with delegating ValueObjectConstResult to calculate its own address when necessary, solves the issue. I have also added a new test case to check for regressions in this area, and checked that existing test cases pass correctly. llvm-svn: 146768
-
- Dec 16, 2011
-
-
Sean Callanan authored
we handle Objective-C method calls. Currently, LLDB treats the result of an Objective-C method as unknown if the type information doesn't have the method's signature. Now Clang can cast the result to id if it isn't explicitly cast. I also added a test case for this, as well as a fix for a type import problem that this feature exposed. llvm-svn: 146756
-
Johnny Chen authored
Simplify the setup leading to the testing of ReadMemory(), ReadCStringFromMemory(), and ReadUnsignedFromMemory(). Instead of getting the location of the variable and converting the hex string to an int, just use val.AddressOf().GetValueAsUnsigned() to compute the address of the memory region to read from. llvm-svn: 146719
-
Johnny Chen authored
Add a test sequence of SBProcess.ReadCStringFromMemory() with (char *)my_char_ptr as the address to read from. char *my_char_ptr = (char *)"Does it work?"; llvm-svn: 146716
-
Johnny Chen authored
Add test scenario for newly added SBProcess APIs: ReadCStringFromMemory() and ReadUnsignedFromMemory(). llvm-svn: 146704
-
- Dec 15, 2011
-
-
Johnny Chen authored
llvm-svn: 146696
-
Johnny Chen authored
Add fuzz calls for newly added SBProcess methods. Fix a typo in the audodoc of SBProcess.ReadCStringFromMemory(). llvm-svn: 146695
-
Johnny Chen authored
Add debug statements for the raw bytes and the disassembled instruction. llvm-svn: 146676
-
Johnny Chen authored
lldb::SBValue::CreateValueFromAddress does not verify SBType::GetPointerType succeeds SBValue::CreateValueFromAddress() should check the validity of type and its derived pointer type before using it. Add a test case. llvm-svn: 146629
-
Sean Callanan authored
clients to disassemble a series of raw bytes as demonstrated by a new testcase. In the future, this API will also allow clients to provide a callback that adds comments for addresses in the disassembly. I also modified the SWIG harness to ensure that Python ByteArrays work as well as strings as sources of raw data. llvm-svn: 146611
-
- Dec 14, 2011
-
-
Johnny Chen authored
LLDBSwigPythonCallCommand crashes when a command script returns an object Add more robustness to LLDBSwigPythonCallCommand. It should check whether the returned Python object is a string, and only assign it as the error msg when the check holds. Also add a regression test. llvm-svn: 146584
-
http://llvm.org/bugs/show_bug.cgi?id=11560Johnny Chen authored
Add null checks to several functions. Plus add test scenario for passing None to SBTarget.FindFirstType(None) and friends. llvm-svn: 146540
-
Johnny Chen authored
llvm-svn: 146539
-
- Dec 13, 2011
-
-
Jim Ingham authored
having the block, then timing out & letting all threads run actually works. llvm-svn: 146471
-
- Dec 12, 2011
-
-
Johnny Chen authored
llvm-svn: 146429
-
Johnny Chen authored
with the recent clang compilers. The latest I tried is: Apple clang version 3.1 (tags/Apple/clang-318.0.9) (based on LLVM 3.1svn) llvm-svn: 146427
-
Johnny Chen authored
There were two problems associated with this radar: 1. "settings show target.source-map" failed to show the source-map after, for example, "settings set target.source-map /Volumes/data/lldb/svn/trunk/test/source-manager /Volumes/data/lldb/svn/trunk/test/source-manager/hidden" has been executed to set the source-map. 2. "list -n main" failed to display the source of the main() function after we properly set the source-map. The first was fixed by adding the missing functionality to TargetInstanceSettings::GetInstanceSettingsValue (Target.cpp) and updating the support files PathMappingList.h/.cpp; the second by modifying SourceManager.cpp to fix several places with incorrect logic. Also added a test case test_move_and_then_display_source() to TestSourceManager.py, which moves main.c to hidden/main.c, sets target.source-map to perform the directory mapping, and then verifies that "list -n main" can still show the main() function. llvm-svn: 146422
-
- Dec 10, 2011
-
-
Johnny Chen authored
Move some print stmts to the test method, where they get printed only if the test is qualified to run under the current test driver run configuration. llvm-svn: 146320
-