FileSpec.GetPath() by default applies de-normalization for a path using a native path syntax.
If host sends a path to a target we can always pass it from host in normalized form (calling FileSpec::GetPath(false)) and denormalize it on a target (FileSpec::GetPath(true)).
I appied such approach only for OpenFile and ModuleInfo requests - if it looks reasonable I will migrate other path-related protocol commands to follow the same style.
Details
Details
- Reviewers
flackr clayborg tberghammer
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Please check what GDB does and try to do the same to keep the protocol compatible with that one (in both direction).
Comment Actions
I haven't found any path requirements for vFile I/O packets in GDB protocol.
My proposal with this CL is to add protection to implementation layer with normalizing path on host side. If target side uses FileSpec to handle received path it can accept both formats - normalized and denormalized.
Comment Actions
AFFECTED FILES
/lldb/trunk/source/Plugins/Platform/gdb-server/PlatformRemoteGDBServer.cpp /lldb/trunk/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp /lldb/trunk/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp
USERS
ovyalov (Author)