Forum Replies Created
-
AuthorPosts
-
lashmuelEParticipant
i copied gdbserver to the deployed machine (same directory where the executable file) and still get the same error message
Attachments:
You must be logged in to view attached files.lashmuelEParticipantHello
The VisualGDb indeed build on one machine and deployed to another machine but until yesterday i did not use gdbserver on the deployed machine.
do i need to copy the gdbserver to the deployed machine? why the VisualGDb did not request it until few days ago?
Best
ShmuelJuly 10, 2023 at 22:36 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #34443lashmuelEParticipantHello,
This time you solve the problem. Thank you!!
lashmuelEParticipantHello,
if it helps you can change the test project definitions so it pass the build and run on your machine and then send it to me for checkmaybe the compiler is not the issue here….
lashmuelEParticipantHello,
All the information you requested in the attached file
Attachments:
You must be logged in to view attached files.lashmuelEParticipantHello,
I did the exact screen shot but still i get error pressing to the failed build line ( Test.cpp(9): error: expected a”;” )
Attached to demo project i used for this problem
Please advise according to this demo project
Attachments:
You must be logged in to view attached files.lashmuelEParticipantAttach the log you requested
Attachments:
You must be logged in to view attached files.lashmuelEParticipantAttached the screen shots you requetsed
Attachments:
You must be logged in to view attached files.lashmuelEParticipantattached the screen shots you request
Attachments:
You must be logged in to view attached files.lashmuelEParticipantHello,
i created test solution for easier problem demonstrationAttachments:
You must be logged in to view attached files.June 22, 2023 at 00:34 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #34389lashmuelEParticipantHello,
Sorry for leaving this post for long time. I wanna solve this issue this time.
Shortly, i created error compilation in file N:\6731_OMFV\SHMUEL\rdpMRS\rdp\dsg_cmp\src\main.cpp. the full path in Linux is /6731_OMFV/SHMUEL/rdpMRS/rdp/dsg_cmp/src/main.cppwhen i tried in Path mapping to define /6731/omfv and in windows section N:/6731_omfv.
when i press the error link i get VisualGDB error dialog: Failed to open ‘/6731_OMFV/SHMUEL/rdpMRS/rdp/dsg_cmp/src\..src\main.cpp(322)’.
Please advise what i must do to get/jump to error line on mouse clickJanuary 25, 2023 at 23:59 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #33757lashmuelEParticipantHello,
i made mistake on the bit.cpp path. the correct path is /6731_omfv/SHMUEL/tdp_develop-linux/tdp/dsg_cmp/src/bit/bit.cpp and not as i mentioned before. so there is a match.
also the window path computed by VisualGDB is n:\6731_omfv\SHMUEL\tdp_develop-linux\tdp\dsc_cmp\src\bit\bit.cpp and not what you mentioned in par 4.so in short there is no inconsistencies as far as i understand.
does it change the your conclusion? do you have other suggestion now?
January 24, 2023 at 04:44 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #33748lashmuelEParticipantHello,
i tried your solution and still doesn’t work
When i press the open directory button and select the 6731_OMV directory (as seen in PathToMountDirectory.JPG) i get automatic complete of $(ProjectDirLinux) to 6731_OMFV as seen in PathMappingAfterSelectLinuxDirectory.JPG
When i manually type the Linux path and start with / i get “nothing found” comment and of course this option also doesn’t work.
Also attached 2 more files to clarify the ProjectDirLinux
Best regards
ShmuelAttachments:
You must be logged in to view attached files.January 23, 2023 at 02:58 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #33740lashmuelEParticipantHello,
The variable $(ProjectDirLinux) was created because i understood that Local directory (windows) and Remote directory (Linux) should point to the same directory where the project file is located.
Since i have $(ProjectDir) that defines automatically the project path to windows and i don’t have such variable for Linux, so i had to create $(ProjectDirLinux).
You wrote “the contents of its directory will be copied to $(ProjectDirLinux)” i guess you meant the compiler output (such as obj files)
you also wrote “it will copy them ALL into the same $(ProjectDirLinux) directory” but the projects in the solution are stored in different directories, hence $(ProjectDirLinux) creates different path for each project.
The full path of bit.cpp in windows is: n:\6731_omfv\SHMUEL\tdp_develop-linux\tdp\dsg_cmp\src\bit.cpp
The full path of project file that include bit.cpp is: n:\6731_omfv\SHMUEL\tdp_develop-linux\tdp\dsc_cmp\projects\rdp.vcxproj
N: is network drive in windows
6731_omfv is folder that mounted from the Linux build machine to N drive hence the full path in Linux to bit.cpp file is: /6731_omfv/SHMUEL/tdp_develop-linux/tdp/dsg_cmp/src/bit.cpp
Also when i go to Custom build steps and press the “Test the command now” (for ProjectDirLinux) i get: “Success: ProjectDirLinux=/6731_omfv/SHMUEL/tdp_develop-linux/tdp/dsg_cmp/projects”Best regards
Shmuel
- This reply was modified 1 year, 11 months ago by support. Reason: highlighted paths
January 12, 2023 at 01:28 in reply to: VisualGDB 5.6 Clean And Source line Build Fail connection #33675lashmuelEParticipantHello,
I created a project as you can see in the screenshot VisualGDBProjectSettings.JPG
I had to create environment variable $(ProjectDirLinux) that defined automatically the Linux project directory as exists in windows at the variable $(ProjectDir). no such variable for Linux.
It Works great for Build and Debug
So i tried to Define the path you suggested in VisualGDB Project Properties -> Synchronized Directories using that variable (ProjectDirLinux) as you can see in VisualGDBSyncDirectories.JPG
then i create a deliberate compile error but when i press error line in FailureLine.JPG i get the error message in VisualGDBFailureOpenException.JPG
What i did wrong?
Best regards
ShmuelAttachments:
You must be logged in to view attached files. -
AuthorPosts