Anyone out there? We really need to get this working, but are having a
difficult time.
From: Steele, Raymond
Sent: Wednesday, January 29, 2014 5:11 PM
To: d...@openoffice.apache.org; api@openoffice.apache.org; Herbert Duerr
(h...@apache.org)
Cc: Meffe, David K
Subject: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory Fault
We've recently compiled OpenOffice 4.01 on Solaris 11 x86 and are experiencing
the following at runtime. I've included some of the stack trace below. Any help
would be great. Thanks!
Observed Behaviour
1. OpenOffice starts, the splash screen with logo appears and then
closes replaced with the full application window and choices for specific
OpenOffice projects.
2. Selecting either the Word or Spreadsheet project causes a
segmentation fault and closes the application.
3. Following the start of the application with the debugger, we can
see the SidebarController is created in a first pass without error (known
because first time to this stop point does not error).
4. As the process continues, the SidebarController constructor is
called a second time (unknown why, but could be understood with more
familiarity with the system).
5. The failure doesn't appear in the constructor, but the trace
follows down SidebarController constructor call of
"WeakReference<SidebarController> WeakController (this);"
6. This template definition for WeakController uses
Reference<Template>::Refrence( interface_type *pInterface) as its definition in
::com::sun::star::uno::Reference.hxx.
7. The function will try to convert the pInterface parameter to a
XInterface type called _pInterface.
8. If it succeeds in converting the pInterface to _pInterface then
the function will try to acquire a new reference.
9. Assumption: Creating this new reference calls
SidebarController::notifyContextChangeEvent with a corrupt or bad rEvent. This
assumption is based on the stack where the immediate next routine after the
Reference function call is the notifyContextChangeEvent, also while following
along in the debugger, the rEvent parameter at this point is already corrupted
with the value <ERROR> stored in the structure.
10. It is later after the notifyContextChangeEvent calls Context and
then ustring that the segmentation fault occurs, but I believe the error
located in rEvent is what causes this later problem.
It appears as if inside the SidebarController Constructor at line 168 when
xWeakController(this) is called that the problem first occurs. The
xWeakController appears to be defined in Reference.hxx in
/cppu/inc/com/sun/star/uno/ and this definition as an inline function that
calls the _pInterface->acquire() at line 136. We assume that this acquire is
where the problem occurs because the
SidebarController::notifyContextChangeEvent (which is the next item on the
stack) rEvent contains an <ERROR> value in the dbxtool (debug tool) immediately
following in the stack. It eventually crashes downstream at line 103 of
ustring.hxx in /sal/inc/rtl when the string is trying to be accessed as pData =
str.pData;
Stack Trace:
(dbx) where
current thread: t@1
=>[1] rtl::OUString::OUString(this = 0xfeff9dac, str = CLASS), line 103 in
"ustring.hxx"
[2] sfx2::sidebar::Context::Context(this = 0xfeff9dac, rsApplication =
CLASS, rsContext = CLASS), line 51 in "Context.cxx"
[3] sfx2::sidebar::SidebarController::notifyContextChangeEvent(this =
0xebc6d6b0, rEvent = STRUCT), line 257 in "SideBarController.cxx"
[4]
com::sun::star::uno::Reference<sfx2::sidebar::SidebarController>::Reference(this
= 0xfeff9f64, pInterface = 0xebc6d6b0), line 136 in "Reference.hxx"
[5] sfx2::sidebar::SidebarController::SidebarController(this = 0xebc6d6b0,
pParentWindow = 0x9659bf8, rxFrame = CLASS), line 168 in "SidebarController.cxx"
I can provide more of the stack trace if needed. Thanks in Advance!
Raymond
