[SailfishDevel] Debug issue from inside the QtCreator IDE

[Juha Kallioinen]

On 09.07.2014 16:15, Iosif Hamlatzis wrote:
> https://www.dropbox.com/s/t6wsbj6sohyq8wd/debug.png
>
>
>
> My system is WindowsXP SP3 and I am using the QtCreator IDE to deploy 
> my game and hopefully debug it.
>
> As you can see from the screenshot (above link) the build and deploy 
> process succeeds (both for the emulator and the actual device).
>
> The problem is I cannot debug my code from inside the IDE either 
> inside the emulator or the actual device. When I select to debug the 
> IDE starts building the game, then it deploys it and then a pop-up 
> dialogue appears requesting an executable (executable files for 
> Windows are .exe - .com - .cmd - .vbs - .bat). BUT the build process 
> doesn't produce any executable file.
>
> Has anyone managed under Windows (any version) to debug on the 
> emulator or device his/her app from inside the IDE?

Debugging does not work in Windows XP, but not because of this problem. 
I can try to explain the problem you are seeing below in case you're 
interested. For Windows XP the ultimate problem is that the gdb binaries 
which can be found from the installdir/bin/gdb-*-meego-linux-gnu*.exe 
are incompatible with Windows XP and can not be run. Windows XP is not 
on the list of supported operating systems, which can be seen in [1].

[1] https://sailfishos.org/alpha_qt5_sdk_release_notes.html

I've created a bug about running gdb in Windows XP to our bug tracker, 
but it's not going to get fixed any time soon.

Now to the problem you're experiencing:

I've understood from your earlier posts that you are working on an SDL 
project. This (to me) means that you've had to create a project either 
from scratch or you have heavily modified the default Sailfish template 
project. Without seeing sources, I can only guess what might be the 
cause for this behavior.

That dialog shown in your screenshot is Qt Creator telling you that it 
does not know which binary to run after deployment. The basic 
requirements for Qt Creator to recognize the application binary are:

Project template type is "app" and the executable binary is either the 
same as the project name or specified by the TARGET variable in the .pro 
file.

If your project's TEMPLATE is other than app and/or you haven't 
specified TARGET, then Qt Creator does not know which binary it needs to 
run after it has deployed the project.

If you don't have the TEMPLATE specified, it is by default "app".

In order to debug anything, Qt Creator would need to know which binary 
it needs to debug. So that is the first step. Additionally it needs to 
run the binary on the remote device (or Emulator), so it needs to know 
what the remote binary will be after deployment. When it knows these, it 
would be able to start a debugging session, but on Windows XP it would 
fail at this point when launching gdb.

Best regards,
  Juha

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20140709/b3f21545/attachment.html>