Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Unhandled exception no stack
Hi guys, strange one, I get an access violation in ole32:
Unhandled exception at 0x755BC8F6 (ole32.dll) in MyApp.exe: 0xC0000005: Access violation reading location 0xFEEEFEEE.but all stack traces of all threads are empty and the error happens when the application is idle so I don't know how to pinpoint the problem. Ideas?
@VRonin mmh, have you tried to replace it? Maybe it went corrupt during the last Windows update, Windows doesn't necessarily tell you when it does updates these days.
I'm pretty sure it's something wrong in my code. The crash happens only when I have a particular dialog open. I'd just like to find a way to identify my bug.
Qt 5.8 MSCV 2013 on Win7 for the record
I have seen that with file dialogs on windows, but I don't think it's anything specific to your code. If I remember correctly the exception happens when the file dialog is initialized somewhere deep in windows' stuff and is "harmless". Try using the alien file dialog (if that's your case).
JonB last edited by
You know a lot more than I do, so I'm only throwing this out there as a possible hint....!
This may not apply because of your ole32 stuff. But often when you cannot get any stack trace at a crash it's indicative that a local variable on the stack has been overwritten beyond the end (like, a local array and you've gone over the end of it) --- that goes up the stack and trashes the call stack information... ?
The release build show no crashes. I honestly don't want to know what was going on there (even though I was using QFileDialog so k's answer was probably correct. Thanks for the help everyone
Out of curiosity, did using Qt's non-native file dialog show a problem of the kind?