To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=42778
User fheckl changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Mar 1 12:00:01 -0800
2005 -------
Ok, further investigations showed me that somehow the static data is
initialized after the method
ImplInitSVData() is called and therefore after pImplSVData has some useful
value.
Here is the relevant part of svdata.cxx:
165 // static SV-Data
166 ImplSVData* pImplSVData = &private_aImplSVData::get();
167
[...]
186 //
===============================================================
========
187
188 void ImplInitSVData()
189 {
190 #ifdef MACOSX
191 if (!pImplSVData)
192 pImplSVData = &private_aImplSVData::get();
193 #endif
And here is what I did in gdb:
(gdb) break svdata.cxx:166
Breakpoint 1 at 0x361594: file
/Volumes/TestDrive/m79/vcl/source/app/svdata.cxx, line 166.
(gdb) break svdata.cxx:191
Breakpoint 2 at 0x1211c: file /Volumes/TestDrive/m79/vcl/source/app/svdata.cxx,
line 191.
(gdb) run
Starting program: /Applications/OpenOffice.org1.9.80/program/testtool.bin
Temporarily disabling shared library breakpoints: 1
Reading symbols for shared libraries
...................................................................................
done
Re-enabling shared library breakpoints: 1
Breakpoint 2, ImplInitSVData() () at
/Volumes/TestDrive/m79/vcl/source/app/svdata.cxx:191
warning: Source file is more recent than executable.
191 if (!pImplSVData)
(gdb) c
Continuing.
Current language: auto; currently c++
Breakpoint 1, __static_initialization_and_destruction_0(int, int)
(__initialize_p=1, __priority=65535) at /
Volumes/TestDrive/m79/vcl/source/app/svdata.cxx:166
166 ImplSVData* pImplSVData = &private_aImplSVData::get();
(gdb)
I tried the same with soffice.bin but there it works normally.
So I suggest that my previously named "workaround" should be dealt as the real
patch for this problem.
---------------------------------------------------------------------
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]
