Meego Wiki
Views

SDK/Docs/1.1/Debugging with Qt Creator

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Create a project with Qt Creator)
Line 2: Line 2:
This is a brief introduction to debugging Qt applications running on a remote MeeGo device, using Qt Creator. The instructions will work with any kind of remote MeeGo device, real or emulated.
This is a brief introduction to debugging Qt applications running on a remote MeeGo device, using Qt Creator. The instructions will work with any kind of remote MeeGo device, real or emulated.
-
 
-
''Verified by [[User:Elliot|Elliot Smith]] on 2010-10-27, with Fedora Core 13 as host and real netbook running trunk as target. Not verified for Windows or other targets yet.''
 
== Prerequisites ==
== Prerequisites ==
-
You will need '''gdb''' to be installed on the host before you can do any debugging with Qt Creator. On Linux, use the package manager to install it;  for example, on Fedora:
+
You will need Qt Creator set up for your operating system: see [[SDK/Docs/1.1/Creating_Hello_World]].
-
sudo yum install gdb
+
You should also setup a new project, configured to deploy to a MeeGo device, as covered in that tutorial.
-
On MeeGo (useful if you're using Qt Creator from a chroot):
+
=== Prepare the host ===
-
zypper install gdb
+
You will need '''gdb''' to be installed on the host before you can do any debugging with Qt Creator. On Linux, use the package manager to install it;  for example, on Fedora:
-
You also need to setup a MeeGo SDK environment:
+
sudo yum install gdb
-
* [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux|SDK on Linux]]
+
=== Configure the Qt Creator project for debugging ===
-
 
+
-
== Configure the project for debugging ==
+
First, ensure that debugging is enabled for the version of Qt in use:
First, ensure that debugging is enabled for the version of Qt in use:
Line 25: Line 21:
# Click on the ''Projects'' button in the left-hand panel.
# Click on the ''Projects'' button in the left-hand panel.
# Under ''General'', click on the ''Manage'' button next to ''Qt Version''.
# Under ''General'', click on the ''Manage'' button next to ''Qt Version''.
-
# Select the Qt version you are using: use the MeeGo Qt version for your particular target (in this case, '''MeeGo 4.7.0''').
+
# Select the Qt version you are using: use the MeeGo Qt version for your particular target (in this case, '''MeeGo sysroot''').
-
# Click on the ''Rebuild'' button next to ''Debugging helpers'' (near the bottom of the dialog box). This builds the debugging helper for this version of Qt.
+
# Click on the ''Rebuild'' button next to ''Debugging helpers'' (near the bottom of the dialog box). This builds the debugging helper for this version of Qt. You should see a green tick under the ''Debugging'' column for that Qt version.
 +
 
 +
=== Set a breakpoint ===
-
Next, you need something to debug. For example, add a ''Push Button'' to the form:
+
Next, you need something to debug. For example, add a ''Push Button'' to the form (defined in <code>mainwindow.ui</code>):
-
[[File:sdk-docs-QtCreator-form-with-push-button.png|800px]]
+
[[File:Sdk-docs-QtCreator-form-with-push-button.png|800px]]
Then add a click handler for it, so that when the button is clicked, a message string is assigned into a variable then output to the console. The code looks like this:
Then add a click handler for it, so that when the button is clicked, a message string is assigned into a variable then output to the console. The code looks like this:
Line 91: Line 89:
</pre>
</pre>
-
Most of this is boilerplate generated when I started the project, but the <code>MainWindow::on_pushButton_clicked</code> method is mine. Notice how it also needs to be defined as a private slot in the header file.
+
Most of this is boilerplate generated the project was started, but the <code>MainWindow::on_pushButton_clicked</code> method is new. Notice how it also needs to be defined as a private slot in the header file.
Add a breakpoint next to the line where you want the debugger to break by clicking in the editor margin. It looks like this:
Add a breakpoint next to the line where you want the debugger to break by clicking in the editor margin. It looks like this:
Line 109: Line 107:
== Debug the application on the device ==
== Debug the application on the device ==
-
To run the application in debug mode, click on the green arrow with a bug overlaid on it (bottom left). This deploys the application to the remote device and starts it, as above; however, it also enables you to debug the remote application inside Qt Creator.
+
To run the application in debug mode, click on the green arrow with a bug overlaid on it (bottom left). This deploys the application to the remote device and starts it, [[SDK/Docs/1.1/Creating_Hello_World#Running the Hello World|as in this tutorial]]; however, it also enables you to debug the remote application inside Qt Creator.
Now, click on the ''Click me!'' button in the application running on the device. The program should pause at the breakpoint. Switch back to Qt Creator and look at the debug panels:
Now, click on the ''Click me!'' button in the application running on the device. The program should pause at the breakpoint. Switch back to Qt Creator and look at the debug panels:

Revision as of 12:49, 29 October 2010


This is a brief introduction to debugging Qt applications running on a remote MeeGo device, using Qt Creator. The instructions will work with any kind of remote MeeGo device, real or emulated.

Contents

Prerequisites

You will need Qt Creator set up for your operating system: see SDK/Docs/1.1/Creating_Hello_World.

You should also setup a new project, configured to deploy to a MeeGo device, as covered in that tutorial.

Prepare the host

You will need gdb to be installed on the host before you can do any debugging with Qt Creator. On Linux, use the package manager to install it; for example, on Fedora:

sudo yum install gdb

Configure the Qt Creator project for debugging

First, ensure that debugging is enabled for the version of Qt in use:

  1. Click on the Projects button in the left-hand panel.
  2. Under General, click on the Manage button next to Qt Version.
  3. Select the Qt version you are using: use the MeeGo Qt version for your particular target (in this case, MeeGo sysroot).
  4. Click on the Rebuild button next to Debugging helpers (near the bottom of the dialog box). This builds the debugging helper for this version of Qt. You should see a green tick under the Debugging column for that Qt version.

Set a breakpoint

Next, you need something to debug. For example, add a Push Button to the form (defined in mainwindow.ui):

Sdk-docs-QtCreator-form-with-push-button.png

Then add a click handler for it, so that when the button is clicked, a message string is assigned into a variable then output to the console. The code looks like this:

/* file: Headers/mainwindow.h */
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <QMainWindow>

namespace Ui {
    class MainWindow;
}

class MainWindow : public QMainWindow
{
    Q_OBJECT

public:
    explicit MainWindow(QWidget *parent = 0);
    ~MainWindow();

private:
    Ui::MainWindow *ui;

// our new handler
private slots:
    void on_pushButton_clicked();
};

#endif // MAINWINDOW_H
/* file: Sources/mainwindow.cpp */
#include "mainwindow.h"
#include "ui_mainwindow.h"
#include <QDebug>
#include <QString>

MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent),
    ui(new Ui::MainWindow)
{
    ui->setupUi(this);
}

MainWindow::~MainWindow()
{
    delete ui;
}

void MainWindow::on_pushButton_clicked()
{
    QString message;
    message = "I have been well and truly clicked";
    qDebug() << message;
}

Most of this is boilerplate generated the project was started, but the MainWindow::on_pushButton_clicked method is new. Notice how it also needs to be defined as a private slot in the header file.

Add a breakpoint next to the line where you want the debugger to break by clicking in the editor margin. It looks like this:

Sdk-docs-QtCreator-set-breakpoint.png

(See the red circle on line 22 after message is initialized.)

To put Qt Creator into debug mode, click on Debug/the bug icon in the left-hand toolbar. This adds some extra panels to the window which are used to show the stack, watch expressions etc.

Next, you need to change the configuration, so that Qt with debugging enabled is used to run the project.

  1. In the left-hand panel, click on Projects.
  2. Under Build Settings, select Debug from the drop-down box next to Edit build configuration.
  3. From the Build menu, select Rebuild all. This recompiles the project using the debug-enabled Qt.

Debug the application on the device

To run the application in debug mode, click on the green arrow with a bug overlaid on it (bottom left). This deploys the application to the remote device and starts it, as in this tutorial; however, it also enables you to debug the remote application inside Qt Creator.

Now, click on the Click me! button in the application running on the device. The program should pause at the breakpoint. Switch back to Qt Creator and look at the debug panels:

Sdk-docs-QtCreator-paused-at-breakpoint.png

The application should pause at the breakpoint; and in Qt Creator, the message variable should then be visible in the Locals and Watchers tab, set to "I have been well and truly clicked".

For more information about using Qt Creator in debug mode, see http://doc.qt.nokia.com/qtcreator-snapshot/creator-debugging.html.

Personal tools