search

OpenOrbis / musl

A PS4 port of musl for the OpenOrbis PS4 Toolchain.
Other
34 stars 9 forks source link

Possible std::cout fix #5

Closed sleirsgoevy closed 2 years ago

sleirsgoevy commented 4 years ago

I have no idea of where fd 1 is routed, but at least (bool)std::cout remains true after a series of writes.

Cryptogenic commented 4 years ago

Unfortunately this doesn't solve the issue either.

std::cout << "Test 1" << std::endl;
std::cout << "Test 2" << std::endl;

still results in:

Test 1[C:\OpenOrbis\PS4Toolchain\\include\\c++\\v1\ostream:787] badbit|failbit set
[test 2 does not print]
sleirsgoevy commented 4 years ago

I can't seem to reproduce the original issue.

  1. Where should I actually see these messages? In the Mira log (9998/tcp) I see nothing. I've verified using a debugger that all messages get written to fd 1.
  2. Does the issue reproduce using the release zip? Or I have to build a debug version from source?

Just in case, clang++ -v reports clang version 7.0.1-8 (tags/RELEASE_701/final) for me.

Cryptogenic commented 2 years ago

std::cout addressed in v1.0 release.