Error -1073741819
-
Why when I create a basic app I get this error : -1073741819
mainwindow.cpp
@#include "mainwindow.h"
#include "ui_mainwindow.h"MainWindow::MainWindow(QWidget *parent) :
QMainWindow(parent),
ui(new Ui::MainWindow)
{
ui->setupUi(this);
}MainWindow::~MainWindow()
{
delete ui;
}
@
main.cpp@#include "mainwindow.h"
#include <QApplication>int main(int argc, char *argv[])
{
QApplication a(argc, argv);
MainWindow w;
w.show();return a.exec();}
@ -
This code seems to be ok but have you run qmake?
If so what line and file is the error referring to? And what is in mainwindow.h header? -
this is in mainwindow.h
@#ifndef MAINWINDOW_H
#define MAINWINDOW_H#include <QMainWindow>
namespace Ui {
class MainWindow;
}
@And i use this for sys root C:\Qt\Qt5.0.1\5.0.1\mingw47_32\bin
@
class MainWindow : public QMainWindow
{
Q_OBJECTpublic:
explicit MainWindow(QWidget *parent = 0);
~MainWindow();private:
Ui::MainWindow *ui;
};#endif // MAINWINDOW_H
@ -
-
Is that your code or Qt code?
I guess it's Qt code? If so, please go backwards in the call stack, starting from the function where it crashed, up to the last function that was still in your code. That would be the place to have a look...
(That's because, most likely, the problem is not in the Qt code where it finally crashed, but in your code that passed wrong/invalid arguments to some Qt function or that tried to call a method on an uninitialized Qt object)
-
[quote author="dwsld" date="1363506638"]I can`t even debug it.[/quote]
Why ???
--
[quote author="dwsld" date="1363506638"]Yes it is Qt code.[/quote]
As said before, just because it crashed in Qt code, this does not necessarily mean the reason for the crash is in Qt code too. Actually, it is more likely that the reason for the crash is in your own code.
For example, if you call a Qt function that takes a pointer to an object of some type, but you pass a NULL pointer (maybe accidentally), then the app will crash in the Qt function - at the place where it tries to dereference the pointer you have passed. So it did crash in Qt code. But the problem that caused the crash, obviously, is in not the Qt code! It is in your code. You never should have passed a NULL pointer where a pointer to an object was required. There are of course many more examples how you can make Qt code crash by using it wrongly...
--
[quote author="dwsld" date="1363506638"]I think that i have not configure the Qt right .Is there a step by step method?[/quote]
What exactly do you mean with "not configure the Qt right"?
Did you build Qt yourself or do you use the pr-compiled Qt libraries?
Think you didn't even mention which platform you are on...
-
Windows 7.I have downloaded this:http://releases.qt-project.org/qt5/5.0.1/qt-windows-opensource-5.0.1-mingw47_32-x86-offline.exe
-
So you did not configure + build Qt yourself, but just use the pre-compiled DLL's, right?
If so, I don't see how you could have configured is wrongly, as you never did (or needed to) configure it.
BTW: Did you read all of my above post(s), especially the part about the stack trace ???
-
[quote author="dwsld" date="1363518510"]How to get the stack trace?[/quote]
That depends on the IDE/Debugger you use, of course.
But if you run a Debug build, inside a Debugger, and then a "crash" occurs, the Debugger will usually trigger a break and then show you where it crashed, including a complete stack trace...
--
Should look like this:
http://i.imgur.com/YNSYMVi.jpgFrom the call stack in this very simple example we can see that it crashed in the fclose() function, from C++ runtime library. But if we go up in the stack trace (only one step in this example), we see that the call came from someFunction() in my own code. And that's exactly where we'll find the actual reason for the crash...
-
-
[quote author="dwsld" date="1363522510"]http://postimage.org/image/lypykxatz/[/quote]
So what happens in the "main_win.cpp" at line 131, which I guess is the only code of yours?