Avoid dirtying the source tree in breakpoint command tests

Description

Avoid dirtying the source tree in breakpoint command tests

Summary:
The paralelization patch exposed a bunch of cases where we were still
touching the source tree (as these tests were now stepping on each
others toes and being flaky).

This patch removes such issues from breakpoint command tests. Since the
only reason they were creating files was to indirectly test whether the
breakpoint commands got executed (and plumbing the full build tree path
to all places that needed it would be messy) I decided to modify the
tests to check for a different side effect instead: modification of a
global variable. This also makes the code simpler as checking the value
of the global variable is easier, and there is nothing to clean up.

As the tests aren't really doing anything debug-info related, I took the
opportunity to also mark them as NO_DEBUG_INFO_TESTCASEs.

Reviewers: jingham, aprantl

Subscribers: lldb-commits

Differential Revision: https://reviews.llvm.org/D43464

Details

Committed
labathFeb 20 2018, 2:24 AM
Differential Revision
D43464: Avoid dirtying the source tree in breakpoint command tests
Parents
rL325569: [llvm-mc] - Produce R_X86_64_PLT32 for "call/jmp foo".
Branches
Unknown
Tags
Unknown