CODEWITHSUNDEEP
windowsdllloader
nurdglaw
nurdglaw

Reputation: 2127

More information following 0xc0000139 error on windows

I'm developing with Qt. Following a tiny change my program now will not start up and if I run the debugger, this dialog box is displayed: enter image description here

I have looked at several other answers to questions about this error and Qt, and they all propose using a different compiler or a different version. I don't believe this will solve my problem.

Searching a little more diligently on Google, I came upon this article, about Visual C++ which suggests, very plausibly, that additional information is available but has been swallowed by one of the tools somewhere. The article goes on to suggest that by changing something in the registry, you can get additional information output when the error occurs. Now, I can run my program from the command line, with minimal intervening tools, so this looked like a really useful idea. Sadly, the link in the article that I believe will tell me more about the required registry change is dead.

Does this ring any bells with anyone? How can I found out the dll and entry point that isn't being found?

Upvotes: 0

Views: 834

Answers (1)

nurdglaw
nurdglaw

Reputation: 2127

Thanks to helpful comments, I managed to get the additional trace enabled using the "image files" tab of gflags.exe. I then found an enormous quantity of trace information on the "Debugger Log" tab of the QCreator debugger.

Close examination showed that the function containing the tiny chnge which kicked off this problem was failing to load.

I have no idea what caused this, but a clean rebuild of the program in question now allows it to run to the point of the original failure that made me want to make a tiny change in the first place.

I guess the moral of the story is to do a clean build immediately when things start getting weird - before trying to pin down the weirdness!

Upvotes: 1

Related Questions