To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73359
User sb changed the following:
What |Old value |New value
================================================================================
Component|framework |udk
--------------------------------------------------------------------------------
Status|NEW |STARTED
--------------------------------------------------------------------------------
OS/Version|Linux |All
--------------------------------------------------------------------------------
QA contact|[EMAIL PROTECTED] |[EMAIL PROTECTED]
--------------------------------------------------------------------------------
Summary|CWS sb66: unopkg list abor|urp_writer thread does not
|ts with bad alloc | terminate cleanly
--------------------------------------------------------------------------------
Target milestone|OOo 2.2 |OOo 2.x
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Jan 11 03:11:28 -0800
2007 -------
[changed Summary]
This has nothing to do with CWS sb66, and little to do with unopkg list. The
problem occurs (sometimes; at least on SRC680m198 unxlngi6.pro) when soffice is
running in parallel with unopkg. In that case, unopkg creates an URP connection
to soffice, and when unopkg terminates, it appears that its urp_writer thread
does not terminate cleanly, see the below stack trace:
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7413d41 in raise () from /lib/tls/libc.so.6
#2 0xb7415529 in abort () from /lib/tls/libc.so.6
#3 0xb75d7ad1 in __gnu_cxx::__verbose_terminate_handler ()
from .../program/libstdc++.so.6
#4 0xb75d5505 in __cxa_call_unexpected ()
from .../program/libstdc++.so.6
#5 0xb75d5542 in std::terminate ()
from .../program/libstdc++.so.6
#6 0xb75d56d2 in __cxa_throw ()
from .../program/libstdc++.so.6
#7 0x0805b3f4 in desktop::Lockfile::~Lockfile ()
[bogus: stripped unopkg.bin]
#8 0x0805b424 in operator new ()
#9 0xb7e03c9a in typelib_typedescriptionreference_getDescription (
ppRet=0xb4a059c0, pRef=0xb52de444)
at SRC680/src.m198/cppu/source/typelib/typelib.cxx:269
#10 0xb41b7efa in bridges_urp::OWriterThread::executeReleaseRemoteCalls (
this=0xb52e472c)
at SRC680/src.m198/bridges/source/remote/urp/urp_writer.cxx:222
#11 0xb41b8035 in bridges_urp::OWriterThread::run (this=0xb52e472c)
at SRC680/src.m198/bridges/source/remote/urp/urp_writer.cxx:267
#12 0xb41a9b6f in threadFunc (param=0xb52e472c) at thread.hxx:196
#13 0xb7e4882f in osl_thread_start_Impl (pData=0x806c030) at thread.c:279
#14 0xb76d77f3 in start_thread () from /lib/tls/libpthread.so.0
#15 0xb74a462a in clone () from /lib/tls/libc.so.6
It appears that TypeDescriptor_Init_Impl::getMutex is called after
TypeDescriptor_Init_Impl::~TypeDescriptor_Init_Impl has already been called.
---------------------------------------------------------------------
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]
