-
-
Notifications
You must be signed in to change notification settings - Fork 924
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
Lever not assigned in Writer via custom LogMessage #666
Labels
Comments
Merged
weaselp
pushed a commit
to weaselp/easyloggingpp
that referenced
this issue
Dec 3, 2019
* upstream/master: update Create FUNDING.yml updated build matrix links Update README.md Update README.md 9.96.7 release updated release updated license generate PIC code for the library Fixed unused variable warning while build without performance logging feature Fix abumq#660 (accessing ELPP before it's initialized) Simplify some code based on already checked values release up removed message Ignore sigint Fixes abumq#666 Set log level from custom message if available Add Emscripten detection, with test modifications
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was originally noticed in residue logging server. Code here
Basically, in Writer construction with custom LogMessage, m_level is not assigned, as a result level's enabled/disabled state is dependent upon undefined behaviour.
This is ignored as a result of this
We need to assign anything that is available in msg as long as they're valid values, especially m_level as it's checked at
construct
The text was updated successfully, but these errors were encountered: