Is there a checklist of "tests" that one can perform to know that their .so file is a valid (or not valid) vis-a-vis XPCOM? How do I debug this? Is the idea that I'm supposed to attach to the regxpcom process during registration (regxpcom) and trace the failure? Or is there an easier way to validate a .so file?
If you have a debug build of mozilla, I would recommend the following procedure using NSPR logging to help track down your error:
export NSPR_LOG_MODULES=nsComponentManager:5 export NSPR_LOG_FILE=/path/log-file-tosave
now run something simple like xpcshell, and then look through the log file for failure messages, especially about your component.
--BDS
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
