forked from qt-creator/qt-creator
Debugger: Use more FilePath in source file handling
Needed for the double-remote case. With this we have proper breakpoint markers in the text editor for a remotely running gdb on a remotely loaded project. Change-Id: If80e4a4108a4a0bcdd7612a59e2bd695213f5ea5 Reviewed-by: Orgad Shaneh <orgads@gmail.com>
This commit is contained in:
@@ -265,7 +265,8 @@ static QString cleanupFullName(const QString &fileName)
|
||||
|
||||
return cleanFilePath;
|
||||
}
|
||||
void BreakpointParameters::updateFromGdbOutput(const GdbMi &bkpt)
|
||||
|
||||
void BreakpointParameters::updateFromGdbOutput(const GdbMi &bkpt, const Utils::FilePath &fileRoot)
|
||||
{
|
||||
QTC_ASSERT(bkpt.isValid(), return);
|
||||
|
||||
@@ -358,7 +359,7 @@ void BreakpointParameters::updateFromGdbOutput(const GdbMi &bkpt)
|
||||
QString name;
|
||||
if (!fullName.isEmpty()) {
|
||||
name = cleanupFullName(fullName);
|
||||
fileName = Utils::FilePath::fromString(name);
|
||||
fileName = fileRoot.withNewPath(name);
|
||||
//if (data->markerFileName().isEmpty())
|
||||
// data->setMarkerFileName(name);
|
||||
} else {
|
||||
@@ -367,7 +368,7 @@ void BreakpointParameters::updateFromGdbOutput(const GdbMi &bkpt)
|
||||
// gdb's own. No point in assigning markerFileName for now.
|
||||
}
|
||||
if (!name.isEmpty())
|
||||
fileName = Utils::FilePath::fromString(name);
|
||||
fileName = fileRoot.withNewPath(name);
|
||||
|
||||
if (fileName.isEmpty())
|
||||
updateLocation(originalLocation);
|
||||
|
||||
Reference in New Issue
Block a user