Console Output Overlap with Multiple async_logger Instances

[yohayonyon]

Hi,

I'm using several async_logger instances across different threads. Each logger is configured with both basic_file_sink_mt and stdout_color_sink_mt. Occasionally, the console output appears to overlap or interleave. I was under the impression that these sink types are thread-safe — could someone clarify why this might be happening? Are there any known limitations or best practices for avoiding this kind of output collision?

tnx

[yohayonyon]

The collision is between a dll that is built separately and the main exe. It makes sense as every one of them has its own thread safety objects.

[tt4g]

See Wiki: https://github.com/gabime/spdlog/wiki/How-to-use-spdlog-in-DLLs

[yohayonyon]

I’ve seen the workaround—thanks for pointing it out.
I’m still getting familiar with how DLLs work. Is there a way to embed the spdlog registry within the DLL itself, so that any application using the DLL can access it?

[yohayonyon]

As far as I understand, if there are a few threads, logs to console from the dll and the main program may still overlap.

[tt4g]

I don't know exactly what is actually going on since the source code is not provided, but
maybe the OS I/O buffer is the culprit. Try flushing the log immediately with spdlog::flush_on(spdlog::level:trace).