VisualGDB Program Output: random blank lines

[hfrmobile]

I am getting random blank lines when printing text via qDebug() to the VisualGDB Program Output window.

1. Why?
2. How can I avoid it?

–hfrmobile

 

[support]

This could be caused by excessive line endings in the printed lines. Our best advice would be to isolate the exact sequence of steps that causes it and then try removing the line endings (or replacing \r\n with \n).

[hfrmobile]

Nope.

qDebug() << “One”;
qDebug() << “Two”;
qDebug() << “Three”;

Sometimes:
One
Two

Three

other times:
One

Two

Three

etc.

To put this in other words: “Someone else” must print the blank lines …

 

• This reply was modified 7 years, 2 months ago by hfrmobile.

[support]

Hi,

Sorry, we are not aware of anything similar. As this looks like a very minor issue, we would suggest simply ignoring it until you get a 100% repro that will make it easy to understand what is causing this.

[pbgrslg]

Hi

I’m using visual GDB since few months and I observe the same issue. To be more precise this is the behavior I have :

My program use “Log4c” library.
– If I start my program through linux shell -> no random blank line
– If I start debugging through VisualGDB -> no random blank line are printed in “Visual GDB remote console” but random additional blank lines appears in “Visual GDB Program Output” window.

I agree about the issue being minor, but I have a 100% repro any time I run any program (C or C++, using \r or \r\n end of line)

This simple example show additional blank line in Visual GDB Program Output for each call to printf (no problem in remote console as usual)
int main(void)
{
while (1)
{
printf(“test\n”);
sleep(1);
}
return 0;
}
OS : Win 10
Visual Studio 2013 & 2015
Visual GDB version 5.2 (build 1374)

• This reply was modified 7 years, 1 month ago by pbgrslg.

[support]

Hi,

Thanks for the repro, we have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.15.1399.msi

[Author]

Posts