Yes!! I wonder why I don't get that anymore?
> Sent: Monday, July 16, 2018 at 10:37 AM
> From: "Nikos Chantziaras"
> To: qt-creator@qt-project.org
> Subject: Re: [Qt-creator] What's the crash?
>
> Seems to be working fine here:
>
>https://i.img
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 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
FWIW I do (sometimes?) get a dialog like Nikos (MSVC 2017):
[image: 2018-07-16 10_29_04-Exception Triggered.jpg]
(What's "The inferior"?)
Once that's dismissed, however, the only place I can find the info is
digging through the debugger log.
It would be useful to indicate in the thread menu whi
Seems to be working fine here:
https://i.imgur.com/OfFSAk5.png
On 16/07/18 17:05, Jason H wrote:
There's nothing more the debugger or C++ can do for you here.
But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
> There's nothing more the debugger or C++ can do for you here.
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, subcod
Hi all,
> Yes, but how do you get the actual crash reason?
You need to inspect the backtrace. You have the local variables for each
function on the stack, and this should give you some insight.
There's nothing more the debugger or C++ can do for you here.
Regards, Andre
>
> On Sat, Jul 14,
Yes, but how do you get the actual crash reason?
On Sat, Jul 14, 2018 at 6:27 AM Nikos Chantziaras wrote:
> On 12/07/18 18:16, Jason H wrote:
> > When my program seg faults, bus errors, or divides by zero, I'm left at
> the offending line in the debugger. Is there a way to tell what exactly
> ca
On 12/07/18 18:16, Jason H wrote:
When my program seg faults, bus errors, or divides by zero, I'm left at the
offending line in the debugger. Is there a way to tell what exactly caused the
crash without having to guess?
You need to do a debug build of your application and then start it in
th
Didn't there used to be some simple dialog that presented that information?
> Sent: Thursday, July 12, 2018 at 11:16 AM
> From: "Jason H"
> To: qt-creator
> Subject: [Qt-creator] What's the crash?
>
> When my program seg faults, bus errors, or divides by z
When my program seg faults, bus errors, or divides by zero, I'm left at the
offending line in the debugger. Is there a way to tell what exactly caused the
crash without having to guess?
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.
10 matches
Mail list logo
