319152 - Provide dlerror string with NS_ERROR_FACTORY_NOT_REGISTERED

Status: RESOLVED WORKSFORME

(Core :: XPCOM, defect)

Description

[Ilya Konstantinov]

When loading a native XPCOM component fails, an NS_ERROR_FACTORY_NOT_REGISTERED is emitted (e.g. from nsIComponentRegistrar.autoRegister). It would be beneficial if the resulting scripting exception contained the error which caused the native component not to load, typically provided by the dlerror function on Unices.

This information is beneficial to the user since it often contains details about missing dependencies, which is a problem that can be remedied by the user. If this information would be available in the resulting exception, the GUI layer could display it in a message box to the user.

Today, the dlerror message is emitted to stderr, but this often is not seen by the end-user.

I don't know whether native XPCOM components (such as nsComponentRegistrar is) can even dispatch custom error messages to scripting, and if so, through which facility, so I'd any info on that matter too.

Comment 1

[Doug Turner (:dougt)]

mass reassigning to nobody.

Comment 2

[Benjamin Smedberg]

There is console logging for most of this now.