qDebug() output limited?

SPlatten

I have a QString that I am processing and stripping out whitespace that isn't included in single or double quotes.

I then dump this to the console using:

    qDebug() << __FILE__ << __LINE__ << strProcessed;

The output I see in the Application Output has been cut short, I know this because I've checked using the debugger and I can see the strProcessed actually contains 3279 bytes of data with no null terminator in the content.

Is there any way to get qDebug to dump everything?

I am using Qt Creator:

    Qt Creator 4.11.2
    Based on Qt 5.14.2 (Clang 10.0 (Apple), 64 bit)
    Built on Mar 27 2020 02:24:45
    From revision 699407b4ba

The project is built for:

    Desktop Qt 5.14.2 clang 64 bit

SPlatten

Actually now the routine where I have the processed output is complete and working the processed output is not much smaller. So its no longer an issue, but good to be aware of for the future.

Christian Ehrlicher

@SPlatten said in qDebug() output limited?:

Is there any way to get qDebug to dump everything?

No.

Taytoo

Qt uses underlying APIs for debug output, in case of Windows it probably uses OutputDebugString which has a limit of less than 4K and looks like you're almost reaching that limit.

Why not just split the strProcessed into smaller strings and output them individually?

SPlatten

Actually now the routine where I have the processed output is complete and working the processed output is not much smaller. So its no longer an issue, but good to be aware of for the future.

Christian Ehrlicher

If you want proper logging output use a proper logging mechanism and no stuff which is only for developers during debugging.

Hernandez

While on linux it works fine, on Windows I'm unable to see any qDebug() output Walgreenslistens. What could possibly be wrong? I'm using the Eclipse integration. I'm pretty sure I'm building a debug version. The run configuration is pointing at MyApp.exe in the debug folder.

Christian Ehrlicher

Don't know why you don't open a new thread since this has nothing to do with the one you hijacked but take a look at the qmake CONFIG option console

Pablo J. Rogina

@SPlatten said in qDebug() output limited?:

So its no longer an issue

So please don't forget to mark your post as solved!