| 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/formatters/TestFormatters.py
|
| dcd2a561c052f302e9955f704bf46628d40ab2e0 |
|
15-Feb-2013 |
Daniel Malea <daniel.malea@intel.com> |
Linux test case cleanup:
- Enable TestFormatters.py: expressions with "new" work
- Enable TestChangeValueAPI.py: llvm.org/PR15039 fixed
- Disable expression_command/call-restarts due to llvm.org/PR15278
- Disable expression_command/call-throws due to ObjC test program
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175287 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 3a91e146f4e40ce9b44af3619551f6b6d9bb3b7f |
|
09-Jan-2013 |
Enrico Granata <egranata@apple.com> |
<rdar://problem/12028723>
Adding useful formatting options to the expression (expr) command.
As a side effect of this change, the -d option now supports the same three-values enumeration that frame variables uses (run, don't run, none) instead of a boolean like it did previously
These options do not apply to print, p or po because these are aliased to not take any options.
In order to use them, use expression or expr.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@171993 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 6475c42148a8ea1ca86e5db465db7eca742d897d |
|
04-Dec-2012 |
Greg Clayton <gclayton@apple.com> |
<rdar://problem/12798131>
Cleaned up the option parsing code to always pass around the short options as integers. Previously we cast this down to "char" and lost some information. I recently added an assert that would detect duplicate short character options which was firing during the test suite.
This fix does the following:
- make sure all short options are treated as "int"
- make sure that short options can be non-printable values when a short option is not required or when an option group is mixed into many commands and a short option is not desired
- fix the help printing to "do the right thing" in all cases. Previously if there were duplicate short character options, it would just not emit help for the duplicates
- fix option parsing when there are duplicates to parse options correctly. Previously the option parsing, when done for an OptionGroup, would just start parsing options incorrectly by omitting table entries and it would end up setting the wrong option value
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@169189 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| f5150e815f01da127bfbaedda7942928eaed3f92 |
|
27-Nov-2012 |
Daniel Malea <daniel.malea@intel.com> |
Mark expected failures on Linux (due to bugzilla #14437)
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168727 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| eec19819898fe77ef409e602de26571c8aec4e99 |
|
20-Nov-2012 |
Daniel Malea <daniel.malea@intel.com> |
Fix incorrect usage of buildDsym() in dwarf test
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168371 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.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/formatters/TestFormatters.py
|
| 79bdaddc38c5d20bf347fe98b4c129746bb66291 |
|
24-Apr-2012 |
Enrico Granata <egranata@apple.com> |
Removing the @expectedFailurei386 decorator from test cases that now work as a result of the latest changes to Value.cpp
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@155419 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 67130e42592e68c3055e7ab5b7a368d89a06f05e |
|
19-Apr-2012 |
Johnny Chen <johnny.chen@apple.com> |
Add expected failure decorators for test cases which are failing for i386 architecture.
Plus fix some test cases to skip/succeed for i386.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@155087 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| a3ed7d834b0e0c6924ac95629e740682bbcd15ba |
|
06-Apr-2012 |
Johnny Chen <johnny.chen@apple.com> |
Add a new option to the test driver, -N dsym or -N dwarf, in order to exclude tests decorated with
either @dsym_test or @dwarf_test to be executed during the testsuite run. There are still lots of
Test*.py files which have not been decorated with the new decorator.
An example:
# From TestMyFirstWatchpoint.py ->
class HelloWatchpointTestCase(TestBase):
mydir = os.path.join("functionalities", "watchpoint", "hello_watchpoint")
@dsym_test
def test_hello_watchpoint_with_dsym_using_watchpoint_set(self):
"""Test a simple sequence of watchpoint creation and watchpoint hit."""
self.buildDsym(dictionary=self.d)
self.setTearDownCleanup(dictionary=self.d)
self.hello_watchpoint()
@dwarf_test
def test_hello_watchpoint_with_dwarf_using_watchpoint_set(self):
"""Test a simple sequence of watchpoint creation and watchpoint hit."""
self.buildDwarf(dictionary=self.d)
self.setTearDownCleanup(dictionary=self.d)
self.hello_watchpoint()
# Invocation ->
[17:50:14] johnny:/Volumes/data/lldb/svn/ToT/test $ ./dotest.py -N dsym -v -p TestMyFirstWatchpoint.py
LLDB build dir: /Volumes/data/lldb/svn/ToT/build/Debug
LLDB-137
Path: /Volumes/data/lldb/svn/ToT
URL: https://johnny@llvm.org/svn/llvm-project/lldb/trunk
Repository Root: https://johnny@llvm.org/svn/llvm-project
Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8
Revision: 154133
Node Kind: directory
Schedule: normal
Last Changed Author: gclayton
Last Changed Rev: 154109
Last Changed Date: 2012-04-05 10:43:02 -0700 (Thu, 05 Apr 2012)
Session logs for test failures/errors/unexpected successes will go into directory '2012-04-05-17_50_49'
Command invoked: python ./dotest.py -N dsym -v -p TestMyFirstWatchpoint.py
compilers=['clang']
Configuration: arch=x86_64 compiler=clang
----------------------------------------------------------------------
Collected 2 tests
1: test_hello_watchpoint_with_dsym_using_watchpoint_set (TestMyFirstWatchpoint.HelloWatchpointTestCase)
Test a simple sequence of watchpoint creation and watchpoint hit. ... skipped 'dsym tests'
2: test_hello_watchpoint_with_dwarf_using_watchpoint_set (TestMyFirstWatchpoint.HelloWatchpointTestCase)
Test a simple sequence of watchpoint creation and watchpoint hit. ... ok
----------------------------------------------------------------------
Ran 2 tests in 1.138s
OK (skipped=1)
Session logs for test failures/errors/unexpected successes can be found in directory '2012-04-05-17_50_49'
[17:50:50] johnny:/Volumes/data/lldb/svn/ToT/test $
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154154 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 60c1006dc2f18925df191f0664b19f467d891076 |
|
25-Mar-2012 |
Eric Christopher <echristo@apple.com> |
Fix method name for output.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@153416 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 8a2a4f8dd31f3228ce323cd2e3c788cbf9f2e7c1 |
|
08-Oct-2011 |
Jim Ingham <jingham@apple.com> |
Fix the last testsuite regression from the apple-names stuff.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@141468 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| a8428a458e779a64c8642fef5d29c7f6cc1b95f9 |
|
22-Sep-2011 |
Sean Callanan <scallanan@apple.com> |
Fixed a problem with the IR interpreter that caused
it to generate result variables that were not bound
to their underlying data. This allowed the SBValue
class to use the interpreter (if possible).
Also made sure that any result variables that point
to stack allocations in the stack frame of the
interpreted expressions do not get live data.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@140285 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 0ae31648a69b60b68b4a45e2778cc2dde133f945 |
|
20-Sep-2011 |
Johnny Chen <johnny.chen@apple.com> |
Add four new expectedFailre decorators to new failures most likely due to r139772 check-in.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@140150 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|
| 915448044bac6fdac22a33cc46697dcb771a8df2 |
|
06-Sep-2011 |
Enrico Granata <granata.enrico@gmail.com> |
Redesign of the interaction between Python and frozen objects:
- introduced two new classes ValueObjectConstResultChild and ValueObjectConstResultImpl: the first one is a ValueObjectChild obtained from
a ValueObjectConstResult, the second is a common implementation backend for VOCR and VOCRCh of method calls meant to read through pointers stored
in frozen objects ; now such reads transparently move from host to target as required
- as a consequence of the above, removed code that made target-memory copies of expression results in several places throughout LLDB, and also
removed code that enabled to recognize an expression result VO as such
- introduced a new GetPointeeData() method in ValueObject that lets you read a given amount of objects of type T from a VO
representing a T* or T[], and doing dereferences transparently
in private layer it returns a DataExtractor ; in public layer it returns an instance of a newly created lldb::SBData
- as GetPointeeData() does the right thing for both frozen and non-frozen ValueObject's, reimplemented ReadPointedString() to use it
en lieu of doing the raw read itself
- introduced a new GetData() method in ValueObject that lets you get a copy of the data that backs the ValueObject (for pointers,
this returns the address without any previous dereferencing steps ; for arrays it actually reads the whole chunk of memory)
in public layer this returns an SBData, just like GetPointeeData()
- introduced a new CreateValueFromData() method in SBValue that lets you create a new SBValue from a chunk of data wrapped in an SBData
the limitation to remember for this kind of SBValue is that they have no address: extracting the address-of for these objects (with any
of GetAddress(), GetLoadAddress() and AddressOf()) will return invalid values
- added several tests to check that "p"-ing objects (STL classes, char* and char[]) will do the right thing
Solved a bug where global pointers to global variables were not dereferenced correctly for display
New target setting "max-string-summary-length" gives the maximum number of characters to show in a string when summarizing it, instead of the hardcoded 128
Solved a bug where the summary for char[] and char* would not be shown if the ValueObject's were dumped via the "p" command
Removed m_pointers_point_to_load_addrs from ValueObject. Introduced a new m_address_type_of_children, which each ValueObject can set to tell the address type
of any pointers and/or references it creates. In the current codebase, this is load address most of the time (the only notable exception being file
addresses that generate file address children UNLESS we have a live process)
Updated help text for summary-string
Fixed an issue in STL formatters where std::stlcontainer::iterator would match the container's synthetic children providers
Edited the syntax and help for some commands to have proper argument types
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@139160 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/expression_command/formatters/TestFormatters.py
|