mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
Bug 503298 - [lldb] Remove workaround for executable not being absolute
The underlying issue was fixed in CDT in commit 783787a
.
Also, even if that code changes under the rug, lldb might be fixed to handle
the working directory anyway.
See https://bugs.llvm.org/show_bug.cgi?id=30265
Change-Id: I8654ec6c601b49fbfb8258c1a80b95c84021410d
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
This commit is contained in:
parent
920f5e3a7f
commit
18c2d84781
1 changed files with 0 additions and 14 deletions
|
@ -391,20 +391,6 @@ public class LLDBLaunch extends GdbLaunch {
|
|||
return null;
|
||||
}
|
||||
|
||||
@Override
|
||||
public String getProgramPath() throws CoreException {
|
||||
IPath path = new Path(super.getProgramPath());
|
||||
|
||||
// FIXME: LLDB-MI only accepts absolute paths for the program. But this
|
||||
// seems to work with the latest version in SVN trunk (Mac) so we will
|
||||
// need to find out in which version this was or will be fixed and stop
|
||||
// doing this work-around if possible.
|
||||
if (!path.isAbsolute()) {
|
||||
path = getGDBWorkingDirectory().append(path);
|
||||
}
|
||||
return path.toOSString();
|
||||
}
|
||||
|
||||
/**
|
||||
* Returns whether or not the LLDB use by this launch has the given trait.
|
||||
*
|
||||
|
|
Loading…
Add table
Reference in a new issue