Hi Jason,
There's nothing more the debugger or C++ can do for you here.
My comment refered to something like this in your code:
QList<int> data;
data[0] = 123;
That will crash in qlist.cpp with index out of range, and not in your
code. Therefore it is not immediately obvious what causes the crash. But
with the stack trace you can find the guilty function.
It's up to you to inspect the stack though. If global variables are
involved, things might get more complicated.
> MS gives this:
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
> I thought earlier versions of QtC had something simular.
Are you working with a debug version of your program?
Regards,
André
But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC
(code=EXC_I386_DIV, subcode=0x0)
frame #0: 0x0000000100000fad a.out`main at main.c:7
4 {
5 int a = 2;
6 int b = 0;
-> 7 return a/b;
I'm pretty sure I remember some dialog appearing saying something about SIGSEGV
(or in this case EXC_ARITHMETIC)?
MS gives this:
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
I thought earlier versions of QtC had something simular.
The difference is:
int *a, *b; *b=0;
return *a / *b;
Here, the problem could be that 'a' is out of process space, or 'b' is 0. If
'a' is a pointer, I don't necessarily know what my address range is. I have to
deduce (and risk being wrong) what the actual crash was, meaning I could waste
time going down the wrong path.
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
