forked from OSchip/llvm-project
[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
This commit is contained in:
parent
af0c828a1e
commit
9f75418e1a
|
@ -0,0 +1,7 @@
|
|||
# Make sure lldb resolves the target path.
|
||||
# RUN: mkdir -p %t/foo
|
||||
# RUN: cd %t/foo
|
||||
# RUN: %clang %p/Inputs/hello.c -g -o a.out
|
||||
# RUN: %lldb -b a.out | FileCheck %s
|
||||
|
||||
# CHECK: Current executable set to '{{.*}}foo{{[/\\\\]+}}a.out'
|
|
@ -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);
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue