History log of /external/lldb/test/expression_command/test/TestExprs.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
f40b0928e7455c7158ea9aa82d7908cc3fe4d1af 30-Jul-2013 Ed Maste <emaste@freebsd.org> tests: Mark expected FreeBSD failures due to pr16697



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@187415 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
96641d89f901d4f7a1b601d56facf4149ba0b381 10-May-2013 Matt Kopec <Matt.Kopec@intel.com> Add temporary fix for calling c++ global/anonymous functions on Linux.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@181613 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
143d54397640c03366b1debbebcfc0afe91b0aab 26-Apr-2013 Matt Kopec <Matt.Kopec@intel.com> Mark tests as expected fail for Linux due to not being able to call/print c++ demangled functions in the global namespace (bugzilla 15854).


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@180623 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
5eebe9455547f566a49baf682210d385e7a4ab7b 25-Jan-2013 Daniel Malea <daniel.malea@intel.com> Disable confirmation prompts for testing
- set auto-confirm to false when running TestExprs (avoid hang when using API)
- set prompt-on-quit to false in test helper (avoid timeout when using lldb CLI)



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@173485 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
b794020ffbd6473c59a6e98be044df50abf7fc30 15-Jan-2013 Jim Ingham <jingham@apple.com> Separated the "expr --unwind-on-error" behavior into two parts, actual errors (i.e. crashes) which continue to be
controlled by the --unwind-on-error flag, and --ignore-breakpoint which separately controls behavior when a called
function hits a breakpoint. For breakpoints, we don't unwind, we either stop, or ignore the breakpoint, which makes
more sense.
Also make both these behaviors globally settable through "settings set".
Also handle the case where a breakpoint command calls code that ends up re-hitting the breakpoint. We were recursing
and crashing. Now we just stop without calling the second command.

<rdar://problem/12986644>
<rdar://problem/9119325>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@172503 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
0c8446cc220c429fb51f8f9864275c8b1c768533 18-Oct-2012 Greg Clayton <gclayton@apple.com> <rdar://problem/12462048>

LLDB changes argv[0] when debugging a symlink. Now we have the notion of argv0 in the target settings:

target.arg0 (string) =

There is also the program argument that are separate from the first argument that have existed for a while:

target.run-args (arguments) =

When running "target create <exe>", we will place the untouched "<exe>" into target.arg0 to ensure when we run, we run with what the user typed. This has been added to the ProcessLaunchInfo and all other needed places so we always carry around the:
- resolved executable path
- argv0
- program args

Some systems may not support separating argv0 from the resolved executable path and the ProcessLaunchInfo needs to carry all of this information along so that each platform can make that decision.




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@166137 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
431d839a33e9a274e705f7a268a1c9de2ffc2da2 22-Sep-2012 Jim Ingham <jingham@apple.com> Fix all the test case breakages caused by folks writing tests all over the place that depended explicitly
on the output of "break set". Please don't do this sort of thing!!!!!


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@164433 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
0a19a1b9c25117854f226256805239d95153ed2d 04-Feb-2012 Greg Clayton <gclayton@apple.com> Convert all python objects in our API to use overload the __str__ method
instead of the __repr__. __repr__ is a function that should return an
expression that can be used to recreate an python object and we were using
it to just return a human readable string.

Fixed a crasher when using the new implementation of SBValue::Cast(SBType).

Thread hardened lldb::SBValue and lldb::SBWatchpoint and did other general
improvements to the API.

Fixed a crasher in lldb::SBValue::GetChildMemberWithName() where we didn't
correctly handle not having a target.




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@149743 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
0fb0bcc9d4e951145e1b8c783652224c09b23af4 04-Aug-2011 Greg Clayton <gclayton@apple.com> Cleaned up the SBType.h file to not include internal headers and reorganized
the SBType implementation classes.

Fixed LLDB core and the test suite to not use deprecated SBValue APIs.

Added a few new APIs to SBValue:

int64_t
SBValue::GetValueAsSigned(int64_t fail_value=0);

uint64_t
SBValue::GetValueAsUnsigned(uint64_t fail_value=0)




git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@136829 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
425b0cf93f509ba63346e56654322b9d9bc91d60 12-Jul-2011 Johnny Chen <johnny.chen@apple.com> Passing in os.ctermid() as the arg for SBTarget.Launch(...) for stdin_path, stdout_path, and stderr_path
is just wrong and resulted in the inferior's output getting mixed into the GDB remote communication's
log file. Change all test cases to not pass os.ctermid() and either use SBTarget.LaunchSimple() or
SBTarget.Launch() and pass None as stdin_path/stdout_path/srderr_path to use a pseudo terminal.

rdar://problem/9716499 program output is getting mixed into the GDB remote communications


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@134940 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
0a18748c2ac2727dbff814eabb8360754a783a3c 11-Jul-2011 Johnny Chen <johnny.chen@apple.com> The lldbtest.TestBase.DebugSBValue(self, val) method call now does not need the frame argument.
Only the val (of SBValue type) argument is needed.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@134915 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
3d8ae4681b81b42a404ad77a231c6f743040e644 16-Jun-2011 Johnny Chen <johnny.chen@apple.com> The extra burden for the Python API test case to assign its process object to self.process
in order to have its process cleaned up (terminated) upon tearDown is gone for good.
Let's simplify a bunch of Python API test cases.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@133097 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
805fec7ec90a09b94bc4515fcac9b2b03bae153b 24-May-2011 Johnny Chen <johnny.chen@apple.com> Now that we have added a post-processing step for adding truth value testing to
those lldb objects which implement the IsValid() method, let's change the rest of
the test suite to use the more compact truth value testing pattern (the Python way).


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@131970 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
fb3058efeaacc2ced967e46842dfc4875b3daf14 13-May-2011 Sean Callanan <scallanan@apple.com> Introduced support for UnknownAnyTy, the Clang type
representing variables whose type must be inferred
from the way they are used. Functions without debug
information now return UnknownAnyTy and must be cast.

Variables with no debug information are not yet using
UnknownAnyTy; instead they are assumed to be void*.
Support for variables of unknown type is coming (and,
in fact, some relevant support functions are included
in this commit) but will take a bit of extra effort.

The testsuite has also been updated to reflect the new
requirement that the result of printf be cast, i.e.

expr (int) printf("Hello world!")


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@131263 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
47342d57ac5ac0bb2da765374229f94d98cb600a 27-Apr-2011 Johnny Chen <johnny.chen@apple.com> Change the rest of lldbutil.py's function names to all lower case formats to be consistent.
And modify the test cases accordingly.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@130314 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
318aaa0b4b593ec3e69c5962bddab10c47066c4f 26-Apr-2011 Johnny Chen <johnny.chen@apple.com> For lldbutil.py, Change a bunch of function names to all lower case formats to be consistent.
And modify the test cases accordingly.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@130174 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
4b1850a428ee4dd737bde68097cd15a8ccb2ecca 04-Feb-2011 Johnny Chen <johnny.chen@apple.com> Modify test scripts to accomodate SBTarget.Launch() API change.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@124828 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
5ec14f83253f65f51cc0aff15ac34c0f32750e5e 23-Jan-2011 Greg Clayton <gclayton@apple.com> Deprecated old forms of SBTarget::Launch. There is not just one and no
SWIG renaming done to work around deprecated APIs.



git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@124075 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
013c574ff1c4640d137b222baaff26c245780065 10-Dec-2010 Johnny Chen <johnny.chen@apple.com> Fix a test method docstring.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121446 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
4f93bf1b34e9828ff630eddb908adfb04e05aadf 10-Dec-2010 Johnny Chen <johnny.chen@apple.com> Add an infrastructure to mark the Python APIs only test using a decorator.
Example:

@python_api_test
def test_evaluate_expression_python(self):
"""Test SBFrame.EvaluateExpression() API for evaluating an expression."""
...

The opposite of Python APIs only test is an lldb command line test, which sends
commands to the lldb command interpreter. Add a '-a' option to the test driver
to skip Python API only tests.

Modify TestExprs.py to mark a test as @python_api_test and remove an @expectedFailure
decorator as the bug has been fixed.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121442 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
f8312226abff13305649464018c05ed3eb9d03e2 09-Dec-2010 Johnny Chen <johnny.chen@apple.com> Add more module docstring.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121421 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
a3a67d4bd57c5c4a6d0a6b05f55b57ffc9623f88 08-Dec-2010 Johnny Chen <johnny.chen@apple.com> Add test_evaluate_expression_python() to exercise SBFrame.EvaluateExpression() Python API.
Launch the process with ['X', 'Y', 'Z'] as the args to make argc == 4 and verify that's the case,
plus some other EvaluateExpression() calls.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121218 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
5045fdce8267fe6d5dee809fd45f66be4bf8feee 08-Dec-2010 Johnny Chen <johnny.chen@apple.com> Use Python raw string literal to avoid escaping the escape sequence and to make
the command given to lldb command interpreter more readable.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121199 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
94756b1afd3871f77e3de7949434bcf7ce97f827 07-Dec-2010 Johnny Chen <johnny.chen@apple.com> Make the various expression command test sequences more strict by also verifying
the results against our golden ones.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121185 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
6369bbb1bf3100e7788ef5bd210d564a3dbe18d6 07-Dec-2010 Johnny Chen <johnny.chen@apple.com> Add a test sequence for test_expr_commands_can_handle_quotes(self):

# runCmd: command alias print_hi expression printf ("\n\tHi!")
# output:
self.runCmd('command alias print_hi expression printf ("\\n\\tHi!")')
# This fails currently.
self.runCmd('print_hi')

and modify existing test sequences to escape the escape character '\ to prevent it
from being interpreted by Python before passing on to the lldb command interpreter.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121183 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py
ecd834d482ef001989d4ce60042e4d018a5ac569 06-Dec-2010 Johnny Chen <johnny.chen@apple.com> Add two test cases to exercise many expression commands:
o test_many_expr_commands()
o test_expr_commands_can_handle_quotes()

Mark test_expr_commands_can_handle_quotes()
as @expectedFailure:

# rdar://problem/8686536
# CommandInterpreter::HandleCommand is stripping \'s from input for WantsRawCommand commands


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@121019 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/test/TestExprs.py