> Can you just start your application via run? Oh - no. That's why I was trying to debug it :-) I was getting this:
08:10:23: The program has unexpectedly finished. 08:10:23: The process was ended forcefully. Ok - found a missing DLL. Dependency walker didn't actually help (listed all DLLs as "not found"), running in the Windows terminal only complained about not finding the Qt libs, but running in cygwin did the trick and output a useful error. Why do I need to use the command line to get that info. Shouldn't I see that in QtC's "Application Output"? And why doesn't a dialog pop up to tell me that "bar.dll is missing" when I run it in QtC? I swear I've seen that before. (And... CDB just... crashes?) I'm obviously not a Windows guy... Thanks David. --- Andy Maloney // https://asmaloney.com twitter ~ @asmaloney <https://twitter.com/asmaloney> On Fri, Jan 15, 2021 at 8:08 AM David Schulz <david.sch...@qt.io> wrote: > exit code -1073741515 is the same as C0000135 Program can't start because > XYZ is missing > > This usually happens when a required dll is missing. Can you just start > your application via run? > > > > To find the missing dll you can either use dependency walker or open a cmd > with the run environment from Project Settings > Run > Environment > Open > Terminal and run your application an error message should popup telling you > which dlls are missing. > > > > David > > > > *From:* Andy <asmalo...@gmail.com> > *Sent:* 15 January 2021 13:57 > *To:* David Schulz <david.sch...@qt.io> > *Cc:* qt-creator <qt-creator@qt-project.org> > *Subject:* Re: [Qt-creator] (Windows) CDB failing in "setup engine" > > > > Thanks David. > > > > Here's a pastebin: https://pastebin.com/Efwb3mEC > > > > eERROR: Process crashed > dCDB PROCESS FINISHED, status 1, exit code -1073741515 > > > > > The symbol search path error can be ignored. > > > > Is there a way to add a note in the output around that point that it is > expected? (Or - less optimal - add to the text at the top?) Spent a good > while trying to track that down. > > > > --- > Andy Maloney // https://asmaloney.com > > twitter ~ @asmaloney <https://twitter.com/asmaloney> > > > > > > > > On Fri, Jan 15, 2021 at 7:47 AM David Schulz <david.sch...@qt.io> wrote: > > Hi Andy, > > > > The symbol search path error can be ignored. This happens just because we > want to prevent that cdb calls home for every module that is loaded into > the debugger. > > Can you paste the full debugger log on your favorite code paster or open a > bug report and attach the debugger log? > > > > Greetings > > David > > > > > > *From:* Qt-creator <qt-creator-boun...@qt-project.org> *On Behalf Of *Andy > *Sent:* 15 January 2021 13:33 > *To:* qt-creator <qt-creator@qt-project.org> > *Subject:* [Qt-creator] (Windows) CDB failing in "setup engine" > > > > I have CDB installed and it is properly set up in the kit. It's been > working until recently. I recently updated to QtC 4.14. (I primarily > develop on macOS, then work on Windows 10, so I'm not using it daily - not > sure exactly when this broke.) > > > > Debugger log: > > > > dCALL: SETUP ENGINE > Launching C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe > -aqtcreatorcdbext.dll -lines -G -c ".idle_cmd !qtcreatorcdbext.idle" -y > ""\^"""\^""" C:\dev\build-Foo-Desktop_Qt_5_15_2_MSVC2019_64bit-Debug\Foo.exe > using C:\Qt\Tools\QtCreator\lib\qtcreatorcdbext64\qtcreatorcdbext.dll of > 2020-12-17 03:10. > C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe running as > 1848 > > Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64 > Using CDB based breakpoint correction. > Copyright (c) Microsoft Corporation. All rights reserved. > CommandLine: > C:\dev\build-HemoSpat-Desktop_Qt_5_15_2_MSVC2019_64bit-Debug\HemoSpat.exe > > Error: Change all symbol paths attempts to access '""' failed: 0x7b - The > filename, directory name, or volume label syntax is incorrect. > > > > > > Looks like it has something to do with the "symbol search path", but as > far as I know I'm not doing anything to that. > > > > I have: > > > > - checked that it's using the x64 not the x86 version > > - repaired Windows 10 SDK 10.1.19041.1 > > - reinstalled Windows 10 SDK 10.1.19041.1 > > > > Any idea what to try next? > > > > --- > Andy Maloney // https://asmaloney.com > > twitter ~ @asmaloney <https://twitter.com/asmaloney> > > > >
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
