Boost C++ Libraries: Ticket #12391: Visual Studio 2010 hangs up when linking boost log object

status changed; resolution set

Andrey Semashev — Fri, 12 Aug 2016 15:33:00 GMT

status new → closed
resolution → invalid

run() should be called in the dedicated thread that is supposed to process log records. When you pass start_thread = true that's effectively what the internal feeding thread does. If you don't start the internal thread, don't call run or feed_records then your log records will pile up in the queue not being processed.

Regarding the compiler hang I suggest you report it to Microsoft.

xinyan.zhang@… — Fri, 12 Aug 2016 18:25:57 GMT

Without "start_thread=true" or explicitly call "run" or "feed_records", I still get the log record. That is strange. Is that log record incorrect or truncated?

Thank you very much.

Andrey Semashev — Fri, 12 Aug 2016 19:02:12 GMT

You could also be calling flush() which forces the buffered records to be processed at the point of this call. Other than that I can't see how records could appear in the output.

BTW, start_thread is true by default, you have to explicitly set it to false to disable the internal thread.

xinyan.zhang@… — Fri, 12 Aug 2016 19:33:29 GMT

Yes, my code explicitly calls "flush()" periodically. That's the reason. Thank you very much.