[Interest] Can't Debug on Windows 7: Invalid parameter passed to C runtime
josiahbryan at gmail.com
Thu Jun 14 15:11:21 CEST 2012
On Wed, Jun 13, 2012 at 5:50 PM, André Pönitz <
andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> On Wed, Jun 13, 2012 at 04:25:59PM -0400, Josiah Bryan wrote:
> > I'm attempting to debug an odd problem wherein my program (http://
> > code.google.com/p/dviz/) crashes when displaying certain UTF-8
> > strings. That's not really why I'm emailing - the problem I'd like
> > your help with is that I'm unable to run the program in "Debug" mode
> > in Qt Creator on Windows 7.
> > I've set the project in Qt Creator to the "Debug" build and tried to
> > run it in the Debugger (F5). The program builds and launches -
> > however, before the main UI can appear, an error dialog titled
> > "Microsoft Visual C++ Runtime Library" appears giving the following
> > error: "This application has requested the Runtime to terminate in an
> > unusual way. Please contact the application's support team for more
> > information."
> > Below the console output from Qt Creator. As you can guess, it does
> > run correctly in "Release" mode in Qt Creator (just crashes when the
> > user performs a certain UI action - hence why I want to run it in
> > Debug mode. Note that it does not crash on linux in gdb or in release
> > mode - so this is specific to Windows and the debugger in Qt Creator.)
> Assuming that the "release" mode takes roughly the same code path
> as the "debug" mode (i.e. no major #ifdef surgery in your code),
> the problems that are indicated by the output
> QObject: Cannot create children for a parent that is in a different
> thread. [...]
> QCoreApplication::applicationFilePath: Please instantiate the
> QApplication object first [...]
> QWidget: Must construct a QApplication before a QPaintDevice
> Invalid parameter passed to C runtime function.
> They would exist in "release" mode as well. So it does not run
> "correctly" there, rather "by accident".
I just looked at the thread errors - that's a problem in Qt's codebase,
specifically inside Phonon - I don't create any threads at the spot it's
but I do create several Phonon objects which could (very likely) create
If I could only figure out where the QWidget error (above) is coming from
and the QCoreApplication::applicationFilePath error is from - that would be
helpful. Heck, I don't even call applicationFilePath once in my entire
codebase - so that's somewhere in Qt again.
Yes, I do use QWidgets (duh :-) but tracking down *which* call to a new
QWidget caused the above error - that's the rub.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest