To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40203
------- Additional comments from [EMAIL PROTECTED] Sun Jan 16 20:18:54 -0800
2005 -------
I would apologize for perhaps complicating the discussion here, but I feel some
improvements could be
made to the documentation or code, and we wouldn't have the problem I described.
I did some investigation with OOo 1.1.4 on Mac OS X, and your clue about the
missing resources was
helpful.
>From documentation I knew to copy the "program/soffice" script as
>"program/testtool", to copy
"automation/unxmacxp.pro/bin/testtool" as "program/testtool.bin", and to make
sure "program/
libsts645mxp.dylib" was copied from the solver, but there was no mention (that
I can find) of making
sure any necessary resources were present. I think I used to copy
"automation/unxmacxp.pro/bin/
tma64501.res" as "program/tma64501.res" or "program/testtool.res" but this was
probably wrong.
I don't know how my previous successes with QATestTool on Mac OS X worked -
apparently for OOo
1.1rc5 and OOo 1.1.1rc3 - because when I searched for "stt*.res" in those
locations, none was found.
Nonetheless if I omitted "stt64501.res" from its correct location in OOo 1.1.4,
I did get a crash as
previously described. Here is the most current crash log :
Host Name: twinpeaks.local
Date/Time: 2005-01-16 18:45:16 -0800
OS Version: 10.3.3 (Build 7F44)
Report Version: 2
Command: testtool.bin
Path: /Volumes/MoreApps/OOo_1.1.4/program/testtool.bin
Version: ??? (???)
PID: 434
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000384
Thread 0 Crashed:
0 libtl645mxp.dylib 0x0041349c ResMgr::GetResource(ResId const&, Resource
const*) + 0x84
(debugprint.cxx:68)
1 libtl645mxp.dylib 0x004118d4 Resource::GetRes(ResId const&) + 0x38
(debugprint.cxx:68)
2 libvcl645mxp.dylib 0x019e9848 Accelerator::ImplLoadRes(ResId const&) + 0x1c
3 libvcl645mxp.dylib 0x019e9818 Accelerator::Accelerator[unified](ResId
const&) + 0xb4
4 testtool.bin 0x0002c82c BasicApp::Main() + 0x478
5 libvcl645mxp.dylib 0x0193ab34 SVMain() + 0x58
6 libvcl645mxp.dylib 0x01aaa19c main + 0x38
7 testtool.bin 0x00001f14 _start + 0x17c (crt.c:267)
8 testtool.bin 0x00001d94 start + 0x30
PPC Thread State:
srr0: 0x0041349c srr1: 0x0200f930 vrsave: 0x00000000
cr: 0x24000422 xer: 0x00000002 lr: 0x00413428 ctr: 0x0041189c
r0: 0x00002329 r1: 0xbffff2f0 r2: 0x0044cc20 r3: 0x00000000
r4: 0x0000011a r5: 0xbffff4f0 r6: 0x00000010 r7: 0x00000000
r8: 0x022023b8 r9: 0x00000400 r10: 0x00411978 r11: 0x01b0b36c
r12: 0x0041189c r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0xbffff4f0
r24: 0xbffff4f0 r25: 0x0000011a r26: 0x00002329 r27: 0x00000000
r28: 0x00000000 r29: 0x00000000 r30: 0xbffff590 r31: 0x00413428
In short, crashing (perhaps there is something wrong with the debugprint.cxx
code) is a poor substitute
for reporting a missing file.
When I copied "stt64501.res" from the solver to
"program/resource/stt64501.res", I was able to at least
launch and run QATestTool.
Maybe this resource file is installed as part of the installation process on
other platforms, but it
certainly isn't on Mac OS X, and I mentioned above, I don't see any reference
to it in the documentation.
I guess I should try to contribute improvements to the whole experience...
Anyway, although I was able to launch and run QATestTool for OOo 1.1.4 on Mac
OS X, when I tried
running the "first.bas" script, it failed with an unknown symbol "get" in one
of the included files. I
haven't tried to track down this yet.
Just for the benefit of other Mac OS X readers, "ktrace" is probably not what
you want. If you are to use
any tool for tracing what files QATestTool opens, use the "fs_usage" tool.
---------------------------------------------------------------------
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]
