QtCreator crashed and now will not start due to segfault
-
I just debugged it and got this: Exception thrown at 0x670E5DA7 (Qt5Core.dll) in qtcreator.exe: 0xC0000005: Access violation reading location 0x7E5B8721.
Is it possible that the wrong Qt DLLs are loaded? Have you changed the PATH environment variable, for example?
-
Hmm I'll try adding it to the PATH xD
EDIT: that didn't work
-
Hmm I'll try adding it to the PATH xD
EDIT: that didn't work
No, that's not what I meant! I meant, have you done before? Or have you installed some program that did?
-
It's not corrupted because it's a clean install
-
-
already did that.
@TMcSquared
Best guess is that it gets wrong QtDLLs maybe via
path. -
My PATH variable has zero Qt paths in it. even after a clean install.
-
My PATH variable has zero Qt paths in it. even after a clean install.
@TMcSquared
I have no idea then.
last test
can you start with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler
from shell and see if still crash ? -
@TMcSquared
I have no idea then.
last test
can you start with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler
from shell and see if still crash ?:O It opened with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler -
Hi,
Then it sounds like a graphic driver issue then. Are you sure there wasn't any modification in that regard on your machine ?
-
Hmm I'll try adding it to the PATH xD
EDIT: that didn't work
@TMcSquared
You could check whether Windows Update snuck in and did anything since it last worked... :) -
That's completely possible, thanks for your guy's help!
@SGaist I have no idea, it quit working while I was logged in. -
Hi all. Sorry to revive this topic but this problem has occurred to me as well but on an application I wrote for a client. The application was running fine. Then it crashed (just like @TMcSquared ) and hasn't opened since.
My access violation is in theQtWidgets.dllmodule.Any clues? (i don't have the welcome/QmlDesigner/etc modules to disable on load as does qtcreatorI)
-
Hi all. Sorry to revive this topic but this problem has occurred to me as well but on an application I wrote for a client. The application was running fine. Then it crashed (just like @TMcSquared ) and hasn't opened since.
My access violation is in theQtWidgets.dllmodule.Any clues? (i don't have the welcome/QmlDesigner/etc modules to disable on load as does qtcreatorI)
@nwoki
Hi
Do you use QML?
if yes, could be a driver issue.Do you have data files?
if yes, it could be damaged data files crashing app on load.It could be client installed other app using Qt dlls and now your app finds the wrong version of Qt dll.
Buts its nearly impossible to guess on without far more concrete information :)
-
@nwoki
Hi
Do you use QML?
if yes, could be a driver issue.Do you have data files?
if yes, it could be damaged data files crashing app on load.It could be client installed other app using Qt dlls and now your app finds the wrong version of Qt dll.
Buts its nearly impossible to guess on without far more concrete information :)
@mrjj said in QtCreator crashed and now will not start due to segfault:
@nwoki
Hi
Do you use QML?
if yes, could be a driver issue.This is reproducable only on the client pc. Any way I can debug this?
Do you have data files?
if yes, it could be damaged data files crashing app on load.Cleaned and still no dice
It could be client installed other app using Qt dlls and now your app finds the wrong version of Qt dll.
No other Qt applications are installed
Buts its nearly impossible to guess on without far more concrete information :)
Any idea on how I can help gather more info for furthur debugging?
-
@mrjj said in QtCreator crashed and now will not start due to segfault:
@nwoki
Hi
Do you use QML?
if yes, could be a driver issue.This is reproducable only on the client pc. Any way I can debug this?
Do you have data files?
if yes, it could be damaged data files crashing app on load.Cleaned and still no dice
It could be client installed other app using Qt dlls and now your app finds the wrong version of Qt dll.
No other Qt applications are installed
Buts its nearly impossible to guess on without far more concrete information :)
Any idea on how I can help gather more info for furthur debugging?
Hi
This is reproducible only on the client pc. Any way I can debug this?
Not really. you can ask him to update drivers and also
collect information about opengl version supported.
I take it, the project does use QML?Any idea on how I can help gather more info for furthur debugging?
Well, i would add some logging to the app.
So you can see if dies before main.
That will give a hint if its related to actual user code or a DLL issue. -
Hi
This is reproducible only on the client pc. Any way I can debug this?
Not really. you can ask him to update drivers and also
collect information about opengl version supported.
I take it, the project does use QML?Any idea on how I can help gather more info for furthur debugging?
Well, i would add some logging to the app.
So you can see if dies before main.
That will give a hint if its related to actual user code or a DLL issue. -
@mrjj doesn't even start, so adding any logging is futile. Double click on app -> immediate crash. I can see the crash errors in the windows EventViewer
@nwoki
Hi
and there is no code in main.cpp that could crash it ?
that is 100% for sure ?Then it really sounds like DLL issue.
Do you know what happens to client pc between app working and crashing ?
Windows update or anything like that ?
