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





------- Additional comments from mcasadev...@openoffice.org Wed Feb 17 11:19:26 
+0000 2010 -------
Still seen with 3.2.0 RC. Did some more digging, testtools successfully passes 
all pyuno test but causes Python to abort. This suggests to me that something 
is 
breaking the stack on ARM in UNO although its not clear where this may be; I've 
yet to get a decent GDB backtrace of the crash.

r...@arm:~/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/testtools/source/bridgetest/pyuno# dmake runtest
start test with  dmake runtest
------------- 
cd ../../../unxlngr.pro/lib && export 
FOO=file:///home/nc/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/testtools/source/bridgetest/pyuno/../../../unxlngr.pro/li
b     UNO_TYPES=pyuno_regcomp.rdb UNO_SERVICES=pyuno_regcomp.rdb && python 
main.py
testStandard (importer.ImporterTestCase) ... ok
testDynamicComponentRegistration (importer.ImporterTestCase) ... ok
testErrors (core.TestCase) ... ok
testBaseTypes (core.TestCase) ... ok
testOutparam (core.TestCase) ... ok
testStruct (core.TestCase) ... ok
testType (core.TestCase) ... ok
testEnum (core.TestCase) ... ok
testBool (core.TestCase) ... ok
testChar (core.TestCase) ... ok
testUnicode (core.TestCase) ... ok
testConstant (core.TestCase) ... ok
testExceptions (core.TestCase) ... ok
testInterface (core.TestCase) ... ok
testByteSequence (core.TestCase) ... ok
testInvoke (core.TestCase) ... ok
testStandard (impl.TestCase) ... ok
testUrlHelper (impl.TestHelperCase) ... ok
testInspect (impl.TestHelperCase) ... ok
testListener (impl.TestHelperCase) ... ok
testCurrentContext (impl.TestHelperCase) ... ok

----------------------------------------------------------------------
Ran 21 tests in 0.571s

OK
Fatal Python error: PyImport_GetModuleDict: no module dictionary!
/bin/bash: line 1: 29354 Aborted                 (core dumped) python main.py
dmake:  Error code 134, while making 'runtest'

When using the jaunty version (OOo 3.0) which allows OOo to run, the output is 
the following:
r...@arm:~/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/testtools/source/bridgetest/pyuno# dmake runtest
start test with  dmake runtest
------------- 
cd ../../../unxlngr.pro/lib && export 
FOO=file:///home/nc/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/testtools/source/bridgetest/pyuno/../../../unxlngr.pro/li
b     UNO_TYPES=pyuno_regcomp.rdb UNO_SERVICES=pyuno_regcomp.rdb && python 
main.py
testStandard (importer.ImporterTestCase) ... ok
testDynamicComponentRegistration (importer.ImporterTestCase) ... ok
testErrors (core.TestCase) ... ok
testBaseTypes (core.TestCase) ... ok
testOutparam (core.TestCase) ... ok
testStruct (core.TestCase) ... ok
testType (core.TestCase) ... ok
testEnum (core.TestCase) ... ok
testBool (core.TestCase) ... ok
testChar (core.TestCase) ... ok
testUnicode (core.TestCase) ... ok
testConstant (core.TestCase) ... ok
testExceptions (core.TestCase) ... ok
testInterface (core.TestCase) ... ok
testByteSequence (core.TestCase) ... ok
testInvoke (core.TestCase) ... ok
testStandard (impl.TestCase) ... ok
testUrlHelper (impl.TestHelperCase) ... ok
testInspect (impl.TestHelperCase) ... ok
testListener (impl.TestHelperCase) ... ok
testCurrentContext (impl.TestHelperCase) ... ok

----------------------------------------------------------------------
Ran 21 tests in 0.577s

OK
cd ../../../unxlngr.pro/lib && export 
FOO=file:///home/nc/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/testtools/source/bridgetest/pyuno/../../../unxlngr.pro/li
b     UNO_TYPES=pyuno_regcomp.rdb UNO_SERVICES=pyuno_regcomp.rdb &&  : &&     
LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/home/nc/src/ooo/openoffic
e.org-3.2.0~rc4/ooo-build/build/OOO320_m11/solver/320/unxlngr.pro/lib 
/home/nc/src/ooo/openoffice.org-3.2.0~rc4/ooo-
build/build/OOO320_m11/solver/320/unxlngr.pro/bin/regcomp -register -br 
pyuno_regcomp.rdb -r dummy.rdb \
                        -l com.sun.star.loader.Python -c 
vnd.openoffice.pymodule:samplecomponent
vnd.openoffice.pymodule:samplecomponent
register component 'vnd.openoffice.pymodule:samplecomponent' in registry 
'dummy.rdb' failed!
error (RuntimeException): python-loader:<type 'exceptions.ImportError'>: No 
module named pythonloader, traceback follows
no traceback available
dmake:  Error code 1, while making 'runtest'

I'm going to move to working against OOo upstream versus Ubuntu source 
packages, 
but I've gotten reports that Debian's OOo is affected on ARM when built with 
GCC 
4.4.


---------------------------------------------------------------------
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: issues-unsubscr...@udk.openoffice.org
For additional commands, e-mail: issues-h...@udk.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to