0xc0000135 only when I use "Release"
-
Hello,
When I build and run Qt in debug deployment mode, my program runs fine. However, when I run it with the release deployment mode, I get the 0xc0000135 error. Please help me, Thank you.
Juan@jrod2much Check whether you have a mix of debug and release libraries in your deployment folder
-
Hello,
When I build and run Qt in debug deployment mode, my program runs fine. However, when I run it with the release deployment mode, I get the 0xc0000135 error. Please help me, Thank you.
Juan@jrod2much make sure you initialize all variables correctly, and pointers to nullptr's.
The debuger/debug build does a lot of that internally, and that, - more often than not - results in a different behaviour between debug and release.
edit:
Race Conditions may also be a thing, theres a destinct difference in how code is executed between debug and release! -
@jrod2much make sure you initialize all variables correctly, and pointers to nullptr's.
The debuger/debug build does a lot of that internally, and that, - more often than not - results in a different behaviour between debug and release.
edit:
Race Conditions may also be a thing, theres a destinct difference in how code is executed between debug and release! -
@jrod2much make sure you initialize all variables correctly, and pointers to nullptr's.
The debuger/debug build does a lot of that internally, and that, - more often than not - results in a different behaviour between debug and release.
edit:
Race Conditions may also be a thing, theres a destinct difference in how code is executed between debug and release!Race Conditions may also be a thing, theres a destinct difference in how code is executed between debug and release!
I trust this comment refers to timing differences only --- you don't mean that debug/release Qt code go about things in a different way, do you?