================ @@ -4,16 +4,16 @@ target create -l "ls" /bin/ls target list -# CHECK: * target #0 (ls): /bin/ls +# CHECK: * target #0 (ls): [[LS_PATH:.*]] ---------------- dzhidzhoev wrote:
> Do I understand correctly here that the path `/bin/ls` is given to target > create, that program is sent to the remote and this LS_PATH will be > `<platform working dir>/ls`? So that's why the substitution is needed. Yes. > Though /bin/ls surely isn't going to be compatible with the remote a large > percentage of the time. I assume it's never actually run. Yes, it only tests labels. > Could make this supported on Windows too if we happen to have some basic C > file hanging around in this dir and use that to make the test binaries > instead, but out of scope for this PR. We can use util names without paths here (to load them from PATH). lldb on Windows will handle that, but I don't know if @medismailben had reasons to use absolute paths. https://github.com/llvm/llvm-project/pull/95986 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
