After yesterdays discussions on determining the CANTUNWIND status of
parts of the OOo stack, I tried to build a version of libgcc that
ignores CANTUNWIND by commenting out the following code segment from
gcc-4.4-4.4.3/src/gcc/config/arm/unwind-arm.c.
/* Can this frame be unwound at all? */
if (eitp->content == EXIDX_CANTUNWIND)
{
UCB_PR_ADDR (ucbp) = 0;
return _URC_END_OF_STACK;
}
I successfully managed to build libgcc with this modification in place,
but I still experience libuno crashes. In addition, I had earlier built
UNO on karmic with jaunty's binutils (2.19 based) which predates the
CANTUNWIND changes that landed in karmic. Now that readelf can read
unwinder information, I'll rebuild karmic with binutils 2.19 and confirm
that we don't have CANTUNWIND segments.
While I'm still sure we're dealing with an unwinder issue, I don't
believe the issue alone is being caused by the CANTUNWIND segments.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
