split.

llvm-svn: 117597

which contains slashes is inconsistent with the meaning of PATH on
Unix-type platforms, and pretty surprising.

If the user has given a specific path to execute and we can't
execute it, we should fail and say why.  (Apparently the new
posix_spawn code doesn't always say why, but that's a separate
issue.)

llvm-svn: 117596

llvm-svn: 117595

llvm-svn: 117592

llvm-svn: 117588

llvm-svn: 117586

llvm-svn: 117585

llvm-svn: 117584

llvm-svn: 117583

Original commit message:

    On "Unix", if Program::FindProgramByName is given a name containing
    slashes, just go with it, regardless of whether it looks like it will
    be executable. This follows the behavior of sh(1) more closely.

It's better when behaviour is consistent between platforms. This change also
makes FindExecutable() behave as expected on unix-likes (before this commit, it
used to always succeed).

llvm-svn: 117582

llvm-svn: 117581

llvm-svn: 117580

llvm-svn: 117577

llvm-svn: 117576

llvm-svn: 117575

familiar with the ownership relationships
involving Diagnostic.

llvm-svn: 117573

llvm-svn: 117572

llvm-svn: 117571

Move the existing patching for undefined symbols so that all the patching
is done in the same function.

llvm-svn: 117570

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

logging for type importing, making errors much
easier to diagnose.  Also removed some Objective-C
related logging.

llvm-svn: 117568

Part 2 of rdar://problem/8595231

llvm-svn: 117567

llvm-svn: 117563

the breakpoint associated with the (filename, line_number) combo when an arrow is pointing to
a source position using Emacs Grand Unified Debugger library to interact with lldb.

The current implmentation is insufficient in that it only asks the breakpoint whether it is
associated with a breakpoint resolver with FileLine type and whether it matches the (filename, line_number)
combo.  There are other breakpoint resolver types whose breakpoint locations can potentially
match the (filename, line_number) combo.

The BreakpointResolver, BreakpointResolverName, BreakpointResolverAddress, and BreakpointResolverFileLine
classes have extra static classof methods to support LLVM style type inquiry through isa, cast, and dyn_cast.

The Breakpoint class has an API method bool GetMatchingFileLine(...) which is invoked from CommandObjectBreak.cpp
to implement the "breakpoint clear" command.

llvm-svn: 117562

llvm-svn: 117561

llvm-svn: 117560

llvm-svn: 117559

Also do some minor refactoring to reduce indentation.

llvm-svn: 117558

Pointed out by Chris!

llvm-svn: 117557

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

to set a breakpoint.

llvm-svn: 117555

Fix http://llvm.org/bugs/show_bug.cgi?id=8493 File name "2010-10-19-14:10:49.059609" is non-portable.

llvm-svn: 117554

llvm-svn: 117553

llvm-svn: 117552

a null pointer.

llvm-svn: 117551

timers to be dumped whenever the ASTUnit is destroyed. Instead, just
print the time elapsed for each operation after we perform the
operation.

llvm-svn: 117550

llvm-svn: 117548

llvm-svn: 117547

llvm-svn: 117546

UnitTests for building all the unit tests.

llvm-svn: 117545