[ooo-build] arm failure to start OOo - terminate called after throwing an instance of 'com::sun::star::ucb::InteractiveAugmentedIOException'

Caolán McNamara caolanm at redhat.com
Fri Sep 4 13:05:58 PDT 2009


On Fri, 2009-09-04 at 11:21 -0500, Chris Cheney wrote:
> Anyone have or have seen this issue before? This is running on the armel
> architecture on Ubuntu.

I haven't seen it, but I've only ever built OOo on debian under qemu
so...

Have you got workspace.cmcfixes59.patch applied ? That's got some fixes
for IA64 and ARM to ensure the desired alignment, i.e. without it an ARM
OOo built on qemu or in kernel lenient mode will auto-detect laxer
alignment that is desirable on arm. There would probably be a kernel
message about bad alignment in this case.

There was some spurious -march in unxlngr.mk in the past, but I think
this is gone now.

It does look like it might be the very first uno exception throw getting
busted (experiment with gdb, break main, catch throw, cont, and see if
its "death on first excecption" which might point to experimenting with
commenting out the #define USE_DOUBLE_MMAP in
bridges/inc/bridges/cpp_uno/shared/vtablefactory.hxx
and seeing if that makes a difference.

Otherwise it might be the the exception code in
bridges/source/cpp_uno/gcc3_linux_arm/except.cxx is wrong, e.g. the bit
inside __ARM_EABI__ but I've no real idea, just some possible clues. 

C.



More information about the ooo-build mailing list