You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.26.0 regression with remote debug: GDB cannot find source files because of lower-casing file paths #346
I noticed on your latest version 0.26.0 that the breakpoint paths and file names are now all lower case.
My source file names and paths have upper-case and lower-case characters.
I am remote debugging from Windows to Linux through ssh.
I was looking forward to your improvements, but for now I guess I will revert to your 0.25.1 version.
More:
If I set "stopAtEntry": true, in my launch.json
Your APP will set a breakpoint at the Src/main.cpp
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Temporary breakpoint 2, main (argc=1, argv=0x7fffffffebc8) at Src/main.cpp:4231\n"}]}
Temporary breakpoint 2, main (argc=1, argv=0x7fffffffebc8) at Src/main.cpp:4231
If I then put a breakpoint in the editor your APP will set the breakpoint like this:
Can you share your launch configuration? I suspect that this has to do with the path mapping configuration between the Windows and Linux machines, but I'd like to get a better understanding of what you currently have setup, so we can replicate the scenario.
This is setting a breakpoint at the same place running older and new
versions of extension.
Version 0.25.1 - THIS WORKS Note the upper-case letters capitalized
GDB -> App:
{"token":15,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[]}}
GDB -> App:
{"token":16,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["bkpt",[["number","2"],["type","breakpoint"],["disp","keep"],["enabled","y"],["addr","0x000000000076b21f"],["func","SetupManager::SetupManager()"],["file","Src/Sys/Admin/SetupManager.cpp"],["fullname","/root/platform/Src/Sys/Admin/SetupManager.cpp"],["line","274"],["thread-groups",["i1"]],["times","0"],["original-location","/root/platform/Src/Sys/Admin/SetupManager.cpp:274"]]]]}}
GDB -> App:
{"token":17,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["bkpt",[["number","3"],["type","breakpoint"],["disp","keep"],["enabled","y"],["addr","0x000000000076b24e"],["func","SetupManager::SetupManager()"],["file","
Src/Sys/Admin/SetupManager.cpp
"],["fullname","/root/platform/Src/Sys/Admin/SetupManager.cpp"],["line","276"],["thread-groups",["i1"]],["times","0"],["original-location","/
root/platform/Src/Sys/Admin/SetupManager.cpp:276"]]]]}}
Version 0.26.0 – THIS DOES NOT WORK
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"log","content":"No
source file named /root/platform/src/sys/admin/setupmanager.cpp.\n"}]}
No source file named /root/platform/src/sys/admin/setupmanager.cpp.
GDB -> App:
{"token":16,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["bkpt",[["number","5"],["type","breakpoint"],["disp","keep"],["enabled","y"],["addr","<PENDING>"],["pending","/root/platform/src/sys/admin/setupmanager.cpp:274"],["times","0"],["original-location","/root/platform/src/sys/admin/setupmanager.cpp:274"]]]]}}
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"log","content":"No
source file named /root/platform/src/sys/admin/setupmanager.cpp.\n"}]}
No source file named /root/platform/src/sys/admin/setupmanager.cpp.
GDB -> App:
{"token":17,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["bkpt",[["number","6"],["type","breakpoint"],["disp","keep"],["enabled","y"],["addr","<PENDING>"],["pending","/
root/platform/src/sys/admin/setupmanager.cpp
:276"],["times","0"],["original-location
","/root/platform/src/sys/admin/setupmanager.cpp:276"]]]]}}
Thanks for that additional information. I'm pretty sure I know where the issue is. I'll take a look at it within the next few days and should be able to generate a new release with this fixed.
On Fri, Apr 22, 2022 at 2:46 PM Troy Brown ***@***.***> wrote:
Thanks for that additional information. I'm pretty sure I know where the
issue is. I'll take a look at it within the next few days and should be
able to generate a new release with this fixed.
—
Reply to this email directly, view it on GitHub
<#346 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALTBDMV7R3UNXYCP4ZBF4DTVGMM3ZANCNFSM5UCR2G4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
changed the title [-]GDB cannot find source files because version 0.26.0 does not respects file path and name case sensitivity. [/-][+]0.26.0 regression with remote debug: GDB cannot find source files because of lower-casing file paths[/+]on Apr 24, 2022
Activity
brownts commentedon Apr 22, 2022
Hi @danocharron, thanks for this report.
Can you share your launch configuration? I suspect that this has to do with the path mapping configuration between the Windows and Linux machines, but I'd like to get a better understanding of what you currently have setup, so we can replicate the scenario.
danocharron commentedon Apr 22, 2022
danocharron commentedon Apr 22, 2022
brownts commentedon Apr 22, 2022
Thanks for that additional information. I'm pretty sure I know where the issue is. I'll take a look at it within the next few days and should be able to generate a new release with this fixed.
danocharron commentedon Apr 22, 2022
GitMensch commentedon Apr 24, 2022
@brownts When working on this can you please check the issue in #332? The main question is where the translation should be done.
[-]GDB cannot find source files because version 0.26.0 does not respects file path and name case sensitivity. [/-][+]0.26.0 regression with remote debug: GDB cannot find source files because of lower-casing file paths[/+]