Resource deadlock would ocur about spdlog

[tt4g]

I don't know because the source code is incomplete.
For example, if m2error() is calling the default logger, it would report error resource deadlock would occur because it re-enters HourlyRotatedFileSinkMt which is not re-entrant, but I can't be sure because your code is incomplete.

[usser0134]

I don't know because the source code is incomplete. For example, if m2error() is calling the default logger, it would report error resource deadlock would occur because it re-enters HourlyRotatedFileSinkMt which is not re-entrant, but I can't be sure because your code is incomplete.

Thank you for reply, i updated first post with m2error

[usser0134]

log.hpp is included in stdafx.h and stdafx.h is included in over 100 cpp files

[tt4g]

std::mutex in HourlyRotatedFileSinkMt is deadlocked because it is accessing the same HourlyRotatedFileSinkMt instance through the default logger from at least m2errror().
Do not access loggers from sink.

[usser0134]

So then, should i create functions for m2error and m2info ?
Log.h

#pragma once

#include <string>

void m2info(const std::string& message);
void m2error(const std::string& message);

template<typename... Args>
void m2info(const std::string& fmt, Args&&... args);

template<typename... Args>
void m2error(const std::string& fmt, Args&&... args);

log.cpp
#include "log.h"
#include <spdlog/spdlog.h>

void m2info(const std::string& message) {
spdlog::info(message);
}

void m2error(const std::string& message) {
spdlog::error(message);
}

template<typename... Args>
void m2info(const std::string& fmt, Args&&... args) {
spdlog::info(fmt, std::forward(args)...);
}

template<typename... Args>
void m2error(const std::string& fmt, Args&&... args) {
spdlog::error(fmt, std::forward(args)...);
}

Should be enough ?

[tt4g]

The design must be such that loggers are not accessed from inside the sink.