[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doubt about -fpic option for compiling objects of shared library
From: |
Matthias Doerfel |
Subject: |
Re: Doubt about -fpic option for compiling objects of shared library |
Date: |
Wed, 05 Oct 2005 14:24:53 +0200 |
User-agent: |
KNode/0.9.0 |
kiran wrote:
> The crash on throw that I mentioned above occurs if
> 1> QT is linked (the QT-3.3.1 which was built on a pentium-4
> machine). AND
> 2> if application uses its custom shared libraries.
> Also crash takes place irrespective of its location.
> We are also using STLPort4.5.3.
>
> Here is the crash stack trace on Xeon:
> #0 0x41416801 in __kill () at __kill:-1
> #1 0x40b6261b in raise (sig=6) at signals.c:65
> #2 0x41417d82 in abort () at ../sysdeps/generic/abort.c:88
> #3 0x400901ab in __default_terminate () at ./libgcc2.c:-1
> #4 0x400901cc in __terminate ()
> from /nfsd0/STLport/Linux/lib/libstlport_gcc.so
> #5 0x40090c9e in __throw () from
> /nfsd0/STLport/Linux/lib/libstlport_gcc.so
> #6 0x40d8488b in CKISCellServices::CheckInstOpen (this=0x81fc310,
> pinst=0x81fc42c) at Source/KISCellServices.cpp:471
Are you really sure that this is a crash? It seems more like an
uncatched exception thrown intentionally in CheckInstOpen().
According to <pan.2005.09.26.07.33.46.853709@users.sf.net> not on all
architectures it is possible to catch exceptions outside a shared
library which have been thrown inside the library.
Regards,
Matthias.