Re: [Boost-bugs] [Boost C++ Libraries] #11923: Boost Log backends fail silently on Ubuntu

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11923: Boost Log backends fail silently on Ubuntu
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-01-26 08:48:02

#11923: Boost Log backends fail silently on Ubuntu
-------------------------------+---------------------
  Reporter:  lylemoffitt@…     |      Owner:  andysem
      Type:  Bugs              |     Status:  closed
 Milestone:  To Be Determined  |  Component:  log
   Version:  Boost 1.55.0      |   Severity:  Problem
Resolution:  invalid           |   Keywords:
-------------------------------+---------------------

Comment (by andysem):

 1. Kubuntu 15.10.
 2. `auto_flush` has no effect on the sink frontend, where the queueing
 happens.
 3. I'm not going to prove anything. You're the one who can reproduce the
 problem, so you're going to have to try the solution. Or not, and live on
 with the problem.
 4. There's no `test_file_backend`. `text_file_backend` only creates the
 file on the first record it receives, so the file will not appear if no
 records reach the backend.

 It's true I didn't notice that the console sink is synchronous. The output
 would have appeared at least on the console, so since you're not getting
 it the problem is elsewhere.

 Upon further inspection I noticed you're using `std::regex` in your
 filter. If you're using gcc 4.8, the official one in 14.04, then it is
 broken and may be the reason why all records are filtered away
 (`std::regex` was actually implemented in
 [https://gcc.gnu.org/gcc-4.9/changes.html 4.9]). Try switching to
 `boost::regex`.

 If that doesn't help, debug your code. See if your filter works. See if
 records reach the sinks. See if any exceptions are thrown. Step through
 the processing of a log record in the debugger.

 ----

 Suck up your emotions and deal with the problem. You're only one able to
 reproduce it, so it's highly likely the source is on your end. I'm not
 paid to read your whining and debug your code, and my time is limited. I
 suggested a possible solution; it may be wrong but that's why you are here
 - to try it out and provide more info. That's how solving the problem
 works. Also, I'm the only maintainer of Boost.Log, so you're unlikely to
 get help elsewhere.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11923#comment:7>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.