Strange behaviors when writing to stdout

[ClementDreptin]

Hi,

I'm pretty sure I found 2 bugs:

• printf calls seem to only print the final line of a buffer.
• std::cout seems to completely skip new line characters.

For example, the following code:

const char content[] = "first line\nsecond line\nthird line\n";
const char finalLine[] = "final line\n";

printf(content);
printf(finalLine);

outputs

third line
final line

The first 2 lines of the content buffer are never printed.

And the following code:

const char content[] = "first line\nsecond line\nthird line\n";
const char finalLine[] = "final line\n";

std::cout << content;
std::cout << finalLine;

outputs

first linesecond linethird linefinal line

The first 2 lines are printed but the new line characters themselves are not.

I tested both the WinForms and ImGui versions and the bugs seem to happen in both.

PS: Thank you so much for this project! I only have an RGH and until recently I was stuck using Xbox Watson, having a debugger that doesn't crash when the console does has been a life saver!

[InvoxiPlayGames]

Do these kinds of prints even work on Xbox Watson when sent from an RGH? I ran into this, or at least the printf one, when developing RB3Enhanced (https://github.com/RBEnhanced/RB3Enhanced/blob/master/source/rb3enhanced.c#L139) and I'm pretty sure it affected Watson as well.

[ClementDreptin]

The behavior isn't 100% correct with Xbox Watson either, but it's closer.

With printf I get:

third line
final line

So 2 blank lines then third and final lines are printed properly.

With std::cout I get:

first line
second line
third line
final line

So everything works as expected.

[ClementDreptin]

I dug a little bit more and it looks like XBDM transmits debug strings differently when using printf and std::cout. For printf, XBDM sends the debug string in a single packet, but for std::cout, it sends a packet for each character.

For this code:

printf("hello\n");

XBDM sends this packet:

debugstr thread=0xf9000000 lf string=hello

And for this code:

std::cout << "hello\n";

XBDM sends this packet:

debugstr thread=0xf9000000 string=h
debugstr thread=0xf9000000 string=e
debugstr thread=0xf9000000 string=l
debugstr thread=0xf9000000 string=l
debugstr thread=0xf9000000 string=o
debugstr thread=0xf9000000 lf string=

The packet parser might not work if the string argument is empty.

For the problem about printing a single buffer containing multiple lines, it's XBDM's fault. I tried the original example and for this code:

const char content[] = "first line\nsecond line\nthird line\n";
printf(content);

XBDM sends this packet:

debugstr thread=0xf9000000 lf string=
debugstr thread=0xf9000000 lf string=
debugstr thread=0xf9000000 lf string=third line

So not much you can do about that.

Hope it helps.