Skip to content

Log if a processor is waiting long for another processor (locks etc) #372

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

Merged
merged 16 commits into from
Apr 26, 2025

Conversation

philippwerner
Copy link
Contributor

  • Write to debug.log if ACQUIRE() waits long
  • Apply wait-time logging to other waiting loops
  • Move some processor functions to platform libs
  • Add some text output functions
  • Reduce memory required for ASSERT() in debug build

@philippwerner philippwerner linked an issue Apr 22, 2025 that may be closed by this pull request
With this change, we may get hints about problems with file I/O in a
freeze case. If debug output visible on screen console does not occur in
debug.log file, this indicates that the freeze is due to file output.
@philippwerner philippwerner self-assigned this Apr 25, 2025
Remove output that causes deadlock when filesystem isn't initalized yet.
Also fix some other issues in error handling.
@krypdkat
Copy link
Contributor

LGTM

@krypdkat krypdkat merged commit 79f2258 into develop Apr 26, 2025
1 check passed
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

Successfully merging this pull request may close these issues.

Track waiting in inter-processor communication (locks etc)
2 participants