• Home
  • History
  • Annotate
  • only in /external/lldb/test/functionalities/target_command/
History log of /external/lldb/test/functionalities/target_command/
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
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
estTargetCommand.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
estTargetCommand.py
6c49bf469d8b43eaab76a43f7a17ac6137a0380c 02-Feb-2012 Johnny Chen <johnny.chen@apple.com> For processes which are not in one of the "launched and stopped" state, 'target variable' command
should use Target::ReadMemory() call to read from the file section offset address.
Also remove the @expectedFailure decorator..

'target variable' command fails if the target program has been run
rdar://problem/9763907


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@149629 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.py
02b6bef8009d2410ed8f3255ce545d42ac5b9b5e 01-Feb-2012 Johnny Chen <johnny.chen@apple.com> Fix indentation.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@149529 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.py
8b3ed5c804322310abdb317cddf5423cb800d934 06-Oct-2011 Johnny Chen <johnny.chen@apple.com> Add a test sequence for 'target variable' command when no arguments are given.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@141264 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.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
estTargetCommand.py
lobals.c
4c1671d0a621a235a1944b1ba48afcf110010a2e 13-Jul-2011 Johnny Chen <johnny.chen@apple.com> Add @expectedFailure decorator for test_target_variable_command_with_dsym().

rdar://problem/9763907


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@135069 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.py
8db6cf5935667b206646bba9a0cc4e4cc8d0f943 13-Jul-2011 Johnny Chen <johnny.chen@apple.com> Add display of a static int variable to the test scenario.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@135016 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.py
lobals.c
192865315e77294605d83a985663ab467270fed0 13-Jul-2011 Johnny Chen <johnny.chen@apple.com> Add a test case to exercise 'target variable' command before and after running the inferior.
Currently it fails after the inferior is run.

rdar://problem/9763907


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@135009 91177308-0d34-0410-b5e6-96231b3b80d8
estTargetCommand.py
lobals.c
e2ac6dec08024429fcc8ef1646a435a732e5e94d 28-Jun-2011 Johnny Chen <johnny.chen@apple.com> Move to plevel dirs stop-hook, target, process_launch, and signal to reside under functionalities.
Rename target dir to target_command.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@133951 91177308-0d34-0410-b5e6-96231b3b80d8
akefile
estTargetCommand.py
.c
.c
.c