From dcae2e2005d38843364b33bf0404658a366b1093 Mon Sep 17 00:00:00 2001 From: "mhammond%skippinet.com.au" Date: Tue, 11 Apr 2006 06:04:23 +0000 Subject: [PATCH] PyXPCOM_LogError should always write the error message, even if there is no traceback or exception info. Not part of the build. git-svn-id: svn://10.0.0.236/trunk@194109 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/extensions/python/xpcom/src/ErrorUtils.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mozilla/extensions/python/xpcom/src/ErrorUtils.cpp b/mozilla/extensions/python/xpcom/src/ErrorUtils.cpp index cf26e3697b2..a13232fbd47 100644 --- a/mozilla/extensions/python/xpcom/src/ErrorUtils.cpp +++ b/mozilla/extensions/python/xpcom/src/ErrorUtils.cpp @@ -215,9 +215,8 @@ PYXPCOM_EXPORT void PyXPCOM_LogError(const char *fmt, ...) PR_vsnprintf(buff, sizeof(buff), fmt, marker); // If we have a Python exception, also log that: nsCAutoString streamout(buff); - if (PyXPCOM_FormatCurrentException(streamout)) { - LogMessage(LOGGER_ERROR, streamout); - } + PyXPCOM_FormatCurrentException(streamout); + LogMessage(LOGGER_ERROR, streamout); } PYXPCOM_EXPORT void PyXPCOM_LogWarning(const char *fmt, ...)