Qt Crashing

jrod2much

Hello,

I am currently working on a project that I have been working on for about 4 weeks. Today, I was editing, building and running as usual and all of a sudden my program started to crash.

10:36:23: Starting C:\Users\rodriguez\Desktop\pixy2-master_V3\pixy2-master\src\host\build-pixymon-New_Kit-Profile\release\PixyMon...
10:36:24: The program has unexpectedly finished.
10:36:24: The process was ended forcefully.
10:36:24: C:/Users/rodriguez/Desktop/pixy2-master_V3/pixy2-master/src/host/build-pixymon-New_Kit-Profile/release/PixyMon crashed.

The output error is: "During startup program exited with code 0xc000135."

This is weird because the program was building and running properly 15 minutes ago. The last thing I did was create a slot for a pushButton so it makes no sense. What do I do? Is there a way to restore my program to how it was this earlier, because Qt constantly autosaves ith the compiling?

VRonin

If you run it with a debugger do you get any more useful output?

Is there a way to restore my program to how it was this earlier

This is one of the scenarios where using source control like git helps a lot

koahnig

@jrod2much

Typically you can restore previous versions of a file by using "undo" functionality (possibly on Ctrl+z, you might need to check).

However, this requires that you know where the change causing the crash happened.

Try to start the debugger, but you need to compile in debug mode first.

sneubert

sometimes it may help to clean an rebuild the project, or to delete the entire build folder

jrod2much

I cleaned and rebuilt it and it worked :)

However, do you know the reliability of the program? Like, will this crashing begin again in the near future?

koahnig

@jrod2much

Sometimes the make process does not cover all dependent files, which may be changed. That was probably the case.
Typically programs do not crash afterwards anymore. It is a good strategy to start a rebuild once in a while. Also when the compiled program does not do what intended.

Probably you forgot to list a file, which can be changed in the .pro file. Therefore, the generated make file cannot cover/detect code changes ends under certain circumtances in a crash or ignores the changes. That is one possible explanation.