Windows On-device debugging: MERSSH & QtCreator "/" vs "\" conflict causes failure

asked 2014-01-02 16:08:11 +0300

tortoisedoc gravatar image

updated 2014-01-02 16:34:38 +0300

pnuu gravatar image
  • Environment : Windows
  • Reproducing: debug on-device
  • Expected results: debugging starts as normal
  • Actual result : debugging fails with message "Project is not included in C:\Users\<username>" (or additional source folder)</username>

Seems like this is due to mishandling of the slashes & backslashes. Two things:

  • MerSSH expectes shared path to be exactly the same as the C:\Users*username*, if not, merssh will fail in substituting the path parts.
  • QtCreator provides VirtualBox Shared path to GDB as replace path; but with \ slashes instead of /, this causes the error "Project is not included in C:\Users*username*"
edit retag flag offensive close delete

Comments

Does this issue only happen on windows? or is linux also affected?

AL13N ( 2014-01-02 22:35:00 +0300 )edit
  • For the merssh, I guess it should be the case.
  • For QtC, I cannot say about Linux unfortunately. But I guess it does not, as VBox will have shares with correct forward slashes instead of backwards (as it has on windows)
tortoisedoc ( 2014-01-03 13:10:47 +0300 )edit

Can you describe the gdb problem more carefully?

Keep in mind that gdb debugging in 1312 SDK is broken and we don't even ship a cross-gdb for ARM with the SDK, so on-device debugging using SDK assets cannot work.

I've fixed some case-sensitivity and / \ problems in merssh/qtcreator, but can't promise that everything works. But I fixed all the cases I ran into. Could you please revisit this report once the update SDK is out.

kaltsi ( 2014-04-08 10:10:03 +0300 )edit

With great pleasure to revisit this once the update is out :-). About the gdb problem, one confusional fact: afaik there is a cross-gdb on the MER vm - perhaps not installed by default, but I do remember David Grease / StsKeeps confirming this.

tortoisedoc ( 2014-04-08 12:02:17 +0300 )edit

Ok there might be some confusion, but I really do happen to know that we don't ship an arm cross-gdb that's configured for Qt Creator use in SDK 1312 :-) It's coming out in the update. If it's in the Mer VM, it's not for Qt Creator.

kaltsi ( 2014-04-08 12:18:59 +0300 )edit