You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
* 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
Fixabumq#660 (accessing ELPP before it's initialized)
Simplify some code based on already checked values
release
up
removed message
Ignore sigint
Fixesabumq#666 Set log level from custom message if available
Add Emscripten detection, with test modifications
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: