Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qemu-eos logging mangles uart log #10

Open
reticulatedpines opened this issue Feb 13, 2023 · 1 comment
Open

qemu-eos logging mangles uart log #10

reticulatedpines opened this issue Feb 13, 2023 · 1 comment

Comments

@reticulatedpines
Copy link
Owner

Both emulated uart and our additional qemu logging goes to stderr. This is unbuffered. It is fairly common for some messages, e.g. DMA logging, to occur while Canon is logging. This causes interleaved output that makes comparing the results of a test run difficult.

Ideally we would be able to know the difference between our logging and Canon output, while also being able to reconstruct order of events. We could log each to separate files, but that makes reconstruction of order hard. We could wrap our output in magic prefix/suffix (a little ugly). We could use some kind of event store (DB, json?) - line by line for uart, fprintf based for our additional logging?

@reticulatedpines
Copy link
Owner Author

The old system seems to use -serial file:somefile.log with qemu, which I assume strips out any qemu-eos direct fprintf() logging. That's probably workable for now but not ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant