8000 Categorization of debug messages in dw_log() · Issue #43 · tomcucinotta/distwalk · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Categorization of debug messages in dw_log() #43

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.

Sign up for GitHub

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

Jump to bottom
Open
deRemo opened this issue Jan 12, 2024 · 3 comments
Open

Categorization of debug messages in dw_log() #43

deRemo opened this issue Jan 12, 2024 · 3 comments

Comments

@deRemo
Copy link
Collaborator
deRemo commented Jan 12, 2024

The dw_log() function is full of clutter that may be not useful for a certain debugging session, making the simple print-and-pray approach more manageable. We need a way to categorize debug information and let the user specify the subset of debug information he's interested in.

Something along the line of

./dw_client -LOG [CONNECTION|STORAGE|ERROR]
@deRemo
Copy link
Collaborator Author
deRemo commented Jan 12, 2024

Check out MongoDB logging system: https://github.com/mongodb/mongo/blob/master/docs/logging.md

@tomcucinotta
Copy link
Owner

https://aquosa.sourceforge.net/aquosa-docs/aquosa-qosres/html/qos__debug_8h.html
:-)!
Features:

  • can specify per-message log level
  • can compare with system-wide or per-module custom log levels
  • can all be compiled out at compile-time, 0 overhead in prod version

But, I don't really think we need it (for now)

@tomcucinotta
Copy link
Owner

Fundamentally the same, but without the kernel compatibility stuff from AQuoSA (you could compile modules in-kernel or in-library):
https://github.com/tomcucinotta/oml/blob/main/oml_debug.h
Same notes as above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tomcucinotta @deRemo
0