Use SAL_WARN, too, to increase chance of actually seeing the message

Passing an, as such useful, verbose error message to the
CannotActivateFactoryException constructor is fairly pointless if that
exception ends up being unexpected and causes program
termination. Which of course is exactly the case when one would be
very interested in seeing any message associated with the exception.

Change-Id: I1cd987669e39e47d5f072690dc5013e4a42fd50a

cppuhelper/source/shlib.cxx

@@ -195,6 +195,7 @@ void cppuhelper::detail::loadSharedLibComponentFactory(
             }
         }
         if (fp == 0) {
+            SAL_WARN("cppuhelper", "unknown factory name \"" << name << "\"");
             throw css::loader::CannotActivateFactoryException(
                 "unknown factory name \"" + name + "\"",
                 css::uno::Reference<css::uno::XInterface>());
@@ -213,6 +214,7 @@ void cppuhelper::detail::loadSharedLibComponentFactory(
                 return;
             }
         }
+        SAL_WARN("cppuhelper", "unknown constructor name \"" << constructor << "\"");
         throw css::loader::CannotActivateFactoryException(
             "unknown constructor name \"" + constructor + "\"",
             css::uno::Reference<css::uno::XInterface>());