This occurs on every install of Necessitas I've done this week (that would be one Win 7, and three on three different Cent OS 6.3 machines) - and it's been this way for the past several months - that is, absolutely no output from my app ever appears in the "Application Output" tab of Qt Creator. Only "Starting remote process ..." (in blue), and then when the app closes, "'org.blah.blah.blah' died" (in red). (And yes, this problem occurs regardless of if I build in Debug or Release mode, or if I build arm 5 or arm 7a, etc. And yes, I see all sorts of output on the console from my app when I build and run it on the linux machine itself, outside of Necessitas.)
I've worked around this (sort of) by adding a custom message handler via
qInstallMsgHandler that intercepts qDebug() output and sends it via a TCP socket to a netcat listner on the network, e.g. nc -l -k 3729. (See
http://code.google.com/p/wifisigmap/source/browse/trunk/MapWindow.cpp#19 - yes, the code is rather hackish - it's not meant to be a sterling example of how to code, rather, just a hack to get at the qDebug() message.)
However, this custom message handler doesn't get (or, rather, my netcat listner doesn't get) messages that occur right on app init, nor does it get messages that occur right before a crash - which would be useful to figure out where the app crashed since the debugger isn't working (see my other thread on that issue.)
So, with the debugger not working, is there a way to get the qDebug() output directly in the "Application Output" tab of Qt Creator? (I vaguely recall this working late last year/earlier this year - but it hasn't worked at all since I started using Necessitas again this summer.)
Thanks for your help!
-Josiah