llvm-svn: 118591

llvm-svn: 118590

llvm-svn: 118511

llvm-svn: 118438

failed/errored tests at the start of the test run, in case the test run crashes
for any reason.  That way, it is easy to locate the session logs for accumulated
failures/errors.

llvm-svn: 118427

llvm-svn: 118415

we want to run just the instance of testclass-testmethod combination and nothing else.

Specifying '-g' now will admit the whole .py test module if it does not contain a matching
testclass-testmethod combination at all.

This option arrangement adheres to the RISC principle of making the common cases fast. :-)

rdar://problem/8584914 Can the default for dotest.py's "-g" flag be switched?

llvm-svn: 118392

identification of the test failures/errors by human beings as well as automatic
processings.

The prefix which identifies the type can be: Error, Failure, or ExpectedFailure.

llvm-svn: 118315

llvm-svn: 118285

llvm-svn: 118279

llvm-svn: 118265

    @unittest2.skip("rdar://problem/8630601 Assertion failed: (result_valobj_sp.get()), function EvaluateExpression, file CommandObjectExpression.cpp, line 227.")

llvm-svn: 118252

    @unittest2.skip("rdar://problem/8630601 Assertion failed: (result_valobj_sp.get()), function EvaluateExpression, file CommandObjectExpression.cpp, line 227.")

llvm-svn: 118251

It should be c's parent frame being a instead of the other way around.

llvm-svn: 118198

local variable and an argument variable.

Add ValueTypeString() utility function into lldbutil.py which converts the enum
into a human readable string.

Modify TestBase.DebugSBValue() to also dump the value type of an SBValue object.

llvm-svn: 118197

idea to also dump the session information for expected failures in addition to
failures and errors (tests with unexpected exceptions).

Modify the LLDBTestResult class which derives from unittest2.TextTestResult to
intercept the addExpectedFailure() method in order to mark the test instance as
needing its session information dumped.

llvm-svn: 118185

llvm-svn: 118180

llvm-svn: 118179

llvm-svn: 118129

Also modify the:

    self.runCmd("expr %s" % var)

to be:

    self.runCmd("expression %s" % var)

since 'expr' is an alias of expression.  And fix the assert message to be either
'frame variable -t %s' or 'expression %s'.

llvm-svn: 118085

Comment out the filtering code.  The next check in will clean up the test case
by wiping off the filtering related logic.

llvm-svn: 118081

    rdar://problem/8464339 test/types directory: b basic_type.cpp:171 does not work, while gdb does work

It tests that 'breakpoint set -f basic_type.cpp:176' works when int.cpp #include's basic_type.cpp.

llvm-svn: 118038

The failures that remain are:

        # rdar://problem/8620735 test/types: frame variable -t a_class_ref.m_b fails
        # The reference type related failures that remain are:
        notnow = set(['a_class_ref.m_b',
                      'a_struct_ref.b',
                      'a_union_nonzero_ref.u.a'])

llvm-svn: 118021

    # rdar://problem/8482903
    # test suite failure for types dir -- "long long" and "unsigned long long"

llvm-svn: 118017

llvm-svn: 117962

getsource_if_available(obj) which also handles the exception if it occurs.

llvm-svn: 117949

                    SBFrame print representation: idx: 0 -> #0

llvm-svn: 117924

llvm-svn: 117730

tests should be near the test summary message, instead of way up in the beginning.

llvm-svn: 117726

    rdar://problem/8584431 Assert in clang while evaluating expression

llvm-svn: 117705

1. FoundationDisassembleTestCase.test_simple_disasm_with_dsym; and
2. FoundationDisassembleTestCase.test_simple_disasm_with_dwarf

the reason being the test was issuing 'disassemble' command to disassemble the current
frame function when stopped.  The 'disassemble' command worked previously but it was a
result of bad option specification.

Fix the disassemble command so that it will require 'disassemble -f' for disassembly of
the current frame function.

llvm-svn: 117688

Change the test case to not check it for an SBVariable's print description.

llvm-svn: 117668

llvm-svn: 117604

If TestBase.expect() is passed an assert message, pass it along when delegating to TestBase.runCmd()
to execute the debugger command.  This will result in a more semantic assert message than just the
command failed message like before:

AssertionError: False is not True : Command 'thread list' returns successfully

And now, we will have:

AssertionError: False is not True : Process state is stopped due to breakpoint
llvm-svn: 117569

File name "2010-10-19-14:10:49.059609" is non-portable.

Do not use ':' in the pathname as it is not permitted on windows platforms.

llvm-svn: 117556

llvm-svn: 117287

llvm-svn: 117281

llvm-svn: 117278

llvm-svn: 117175

llvm-svn: 117152