summaryrefslogtreecommitdiffstats
path: root/lldb/source/Commands
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-08-07 16:21:40 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-08-07 16:21:40 +0000
commit9f75418e1a7edf8f4951e8d86d42bcf97ca64671 (patch)
tree94699d057aa0822d1ee2f27d3294ba6632c2cd54 /lldb/source/Commands
parentaf0c828a1ef2a85e8e98d97e8f72d985ed08fe6f (diff)
downloadbcm5719-llvm-9f75418e1a7edf8f4951e8d86d42bcf97ca64671.tar.gz
bcm5719-llvm-9f75418e1a7edf8f4951e8d86d42bcf97ca64671.zip
[Driver] Expand the executable path in the target create output
Resolve the path in the target create output. This is nice when passing relative paths to the lldb command line driver. $ lldb ./binary (lldb) target create "./binary" Current executable set to '/absolute/path/to/binary' (x86_64). This change only affects the target create output and does not change the debugger's behavior. It doesn't resolve symbolic links so it won't cause confusing when debugging something like clang++ that's symlinked to clang. Differential revision: https://reviews.llvm.org/D65611 llvm-svn: 368182
Diffstat (limited to 'lldb/source/Commands')
-rw-r--r--lldb/source/Commands/CommandObjectTarget.cpp3
1 files changed, 2 insertions, 1 deletions
diff --git a/lldb/source/Commands/CommandObjectTarget.cpp b/lldb/source/Commands/CommandObjectTarget.cpp
index 52a77314e8f..b1879c12904 100644
--- a/lldb/source/Commands/CommandObjectTarget.cpp
+++ b/lldb/source/Commands/CommandObjectTarget.cpp
@@ -450,7 +450,8 @@ protected:
}
} else {
result.AppendMessageWithFormat(
- "Current executable set to '%s' (%s).\n", file_path,
+ "Current executable set to '%s' (%s).\n",
+ file_spec.GetPath().c_str(),
target_sp->GetArchitecture().GetArchitectureName());
result.SetStatus(eReturnStatusSuccessFinishNoResult);
}
OpenPOWER on IntegriCloud