diff options
author | Kai Koehne <kai.koehne@nokia.com> | 2012-08-28 09:22:06 +0200 |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2012-08-30 06:22:45 +0200 |
commit | f7de5b09234e7dd735d91a7b332d841ca6c6fe53 (patch) | |
tree | a94396da220e59228c2632538d8d22285d5177fc /src/corelib/global/qlogging.cpp | |
parent | 7cea395d1f4b1e875cc14930e56a6ea2dea0c9a7 (diff) |
Logging: Remove mutex for OutputDebugString
OutputDebugString seems indeed to be thread safe, at least according
to http://www.unixwiz.net/techtips/outputdebugstring.html . I also didn't
manage to run into any deadlocks on Windows 7 ...
The comment + code was already there (in qcoreapplication_win.cpp) in
the first git commit that imported Qt.
Change-Id: I442e22575558958ef21ab8c6b4cc8b03aee906b2
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'src/corelib/global/qlogging.cpp')
-rw-r--r-- | src/corelib/global/qlogging.cpp | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/corelib/global/qlogging.cpp b/src/corelib/global/qlogging.cpp index ca85ad25cb..64bc3b2726 100644 --- a/src/corelib/global/qlogging.cpp +++ b/src/corelib/global/qlogging.cpp @@ -710,9 +710,6 @@ static void qDefaultMessageHandler(QtMsgType type, const QMessageLogContext &con if (usingWinMain) #endif { - // OutputDebugString is not threadsafe. - static QBasicMutex outputDebugStringMutex; - QMutexLocker locker(&outputDebugStringMutex); OutputDebugString(reinterpret_cast<const wchar_t *>(logMessage.utf16())); return; } |