https://svn.boost.org/trac10/ticket/10242 <p> I have attached a simplified repro case. </p> <p> Setting a filter on the core will affect how attributes are removed an added from logger objects. </p> <p> If the filter is set, removing and then adding attributes will fail on a logger object. </p> <p> If no filter is set, removing and adding attributes works as expected. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10242 Trac 1.4.3 Kent Knox <kent.knox@…> Thu, 24 Jul 2014 20:44:33 GMT https://svn.boost.org/trac10/ticket/10242 https://svn.boost.org/trac10/ticket/10242 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">boostLogger.cpp</span> </li> </ul> <p> Notice the comments tagged with BUG </p> Ticket Andrey Semashev Sat, 26 Jul 2014 16:03:27 GMT https://svn.boost.org/trac10/ticket/10242#comment:1 https://svn.boost.org/trac10/ticket/10242#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> This is not a bug. When you call remove_all_attributes on the logger the first time you also remove the severity attribute from the logger. This doesn't matter when the filter is not set since in that case severity is not used anywhere. But when the filter is set, it doesn't find the severity in the second and third log records and returns false which results in discarding these records. </p> Ticket