malaperle added inline comments.
================ Comment at: lit/tools/lldb-mi/breakpoint/break-insert-enable-pending.test:4 +# +# RUN: %cc -o b.exe %p/inputs/break-insert-pending.c -g +# RUN: %lldbmi < %s | FileCheck %s ---------------- apolyakov wrote: > malaperle wrote: > > apolyakov wrote: > > > As far as your first command is `file-exec-and-symbols`, the best way is > > > to use a generic executable's name. Here it should be: > > > ``` > > > # RUN: %cc -o %t %p/inputs/break-insert-pending.c -g > > > # RUN: %lldbmi %t < %s | FileCheck %s > > > ``` > > How can I use %t for the second file-exec-and-symbols? It doesn't seem to > > work > Should you use `file-exec-and-symbols` two times? AFAIK, after exiting a > program, your target remains the same, so you don't need to load it again. I did that so that printf would not be resolved in order to test that it behaves properly after turning off pending breakpoints. But I can -break-insert printf on a different, non-existent symbol and it should be OK I think. https://reviews.llvm.org/D52953 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
