Strange memory leak

[Raadush]

No, no double deletion.

I have changed the code in such a way, that I neither use global nor 'this' in constructor:

#include "mainwindow.h"
#include <QProgressDialog>
 
MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
{
    QProgressDialog dialog;
    dialog.setValue(50);
    dialog.exec();
}
 
MainWindow::~MainWindow()
{
 
}

#include "mainwindow.h"
#include <QProgressDialog>

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
{
    QProgressDialog dialog;
    dialog.setValue(50);
    dialog.exec();
}

MainWindow::~MainWindow()
{

}

To copy to clipboard, switch view to plain text mode 

Still getting:

Conditional jump or move depends on uninitialised value(s)
in MainWindow::MainWindow(QWidget*) in mainwindow.cpp:8
1: __divdi3 in /usr/lib/libgcc_s-4.7.2-20120921.so.1
2: QElapsedTimer::elapsed() const in /usr/lib/libQtCore.so.4.8.2
3: QProgressDialog::setValue(int) in /usr/lib/libQtGui.so.4.8.2
4: MainWindow::MainWindow(QWidget*) in <a href="file:///home/radek/Development/LeakTest/mainwindow.cpp:8" >mainwindow.cpp:8</a>
5: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>
Uninitialised value was created by a heap allocation 1: operator new(unsigned int) in /builddir/build/BUILD/valgrind-3.7.0/coregrind/m_replacemalloc/vg_replace_malloc.c:282
2: QProgressDialog::QProgressDialog(QWidget*, QFlags&lt;Qt::WindowType&gt in /usr/lib/libQtGui.so.4.8.2
3: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>

Conditional jump or move depends on uninitialised value(s)
in MainWindow::MainWindow(QWidget*) in mainwindow.cpp:8
1: __divdi3 in /usr/lib/libgcc_s-4.7.2-20120921.so.1
2: QElapsedTimer::elapsed() const in /usr/lib/libQtCore.so.4.8.2
3: QProgressDialog::setValue(int) in /usr/lib/libQtGui.so.4.8.2
4: MainWindow::MainWindow(QWidget*) in <a href="file:///home/radek/Development/LeakTest/mainwindow.cpp:8" >mainwindow.cpp:8</a>
5: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>
Uninitialised value was created by a heap allocation 1: operator new(unsigned int) in /builddir/build/BUILD/valgrind-3.7.0/coregrind/m_replacemalloc/vg_replace_malloc.c:282
2: QProgressDialog::QProgressDialog(QWidget*, QFlags&lt;Qt::WindowType&gt in /usr/lib/libQtGui.so.4.8.2
3: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>

Conditional jump or move depends on uninitialised value(s)
in MainWindow::MainWindow(QWidget*) in mainwindow.cpp:8
1: QProgressDialog::setValue(int) in /usr/lib/libQtGui.so.4.8.2
2: MainWindow::MainWindow(QWidget*) in <a href="file:///home/radek/Development/LeakTest/mainwindow.cpp:8" >mainwindow.cpp:8</a>
3: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>
Uninitialised value was created by a heap allocation 1: operator new(unsigned int) in /builddir/build/BUILD/valgrind-3.7.0/coregrind/m_replacemalloc/vg_replace_malloc.c:282
2: QProgressDialog::QProgressDialog(QWidget*, QFlags&lt;Qt::WindowType&gt in /usr/lib/libQtGui.so.4.8.2
3: main in <a href="file:///home/radek/Development/LeakTest/main.cpp:7" >main.cpp:7</a>

[wysota]

So where are the memory leaks? I can only see some warnings about branching, nothing about memory leaks.

[Raadush]

Yes, I admit the topic name is wrong, cause when I started to write my question, I had leak there, but then I realized my mistake, corrected it, which caused those conditional jumps to appear, but I forgot to correct post name. My question is rather why im getting theese and can they be somehow corrected by myself? It's getting harder to find my own errors, when Im flooded with like 20-30 conditional jump errors everytime I call setValue in some place in my application. I know there is a suppression file, but I'd rather understand why Im getting those errors and try to correct them rather then simply ingore them.

[wysota]

My question is rather why im getting theese and can they be somehow corrected by myself?

Are you getting any errors because of these messages? If not then I'd assume these are false positives. You won't be correcting gcc runtime anyway, right?

On the other hand launching a dialog from inside a widget constructor is a really weird thing to do...

[Raadush]

Ok, thanks for your help. Im quite certain they are false positives. In my application Im not calling it from constructor, but here I wanted to reproduce the error with smallest compilable example.