To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100159





------- Additional comments from [email protected] Mon Apr 26 11:46:46 +0000 
2010 -------
Observed what is probably the same problem on DEV300_m77 based CWS sb120,
unxmacxi non-pro, when executing configmgr/qa/unoapi:  Stdout/err output
mentions "terminate called after throwing an instance of
com::sun::star::uno::RuntimeException'" and stack trace is

(gdb) where
#0  0x96ef862e in __ovfl_delete ()
#1  0x96ef868a in abort ()
#2  0x92ee5005 in _CUICopyIconURL ()
#3  0x92ee310c in _CUICopyIconURL ()
#4  0x92ee314b in _CUICopyIconURL ()
#5  0x92ee3261 in _CUICopyIconURL ()
#6  0x019799e3 in ucbhelper::getContentBroker ()
#7  0x0197a12b in ucbhelper::Content::Content ()
#8  0x18d794f3 in io_FileAccess::OFileAccess::getFolderContents ()
#9  0x18a2b1f9 in (anonymous namespace)::getLogStoragefiles ()
#10 0x18a2b750 in oooimprovement::LogStorage::clear ()
#11 0x18a2bfd1 in (anonymous namespace)::OnLogRotateThread::run ()
#12 0x18a333ba in threadFunc ()
#13 0x001fd5b7 in osl_thread_start_Impl ()
#14 0x96e3d155 in _pthread_start ()
#15 0x96e3d012 in thread_start ()

where the _CUICopyIconURL frames are inside libstdc++ (so this is probably
throwing the "No Content Broker!" exception from
ucbhelper/source/client/content.cxx leading to terminate/abort), and the main
thread is already in DestroyApplicationServiceManager within DeInitVCL.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to