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, 2018 at 6:27 AM Nikos Chantziaras <rea...@gmail.com> 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 > > caused the crash without having to guess? > > > > You need to do a debug build of your application and then start it in > > the debugger (just press F5.) This will give you the line of the crash > > but also a backtrace to see how you got to that current line. > > > > _______________________________________________ > > Qt-creator mailing list > > Qt-creator@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/qt-creator > > > -- Von meinem Jolla gesendet _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
