This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Fwd: _Unwind_Resume on the stack
No, We have compiled our application on RHEL 3 with libgcc-3.2.3-34.
On Jan 29, 2008 3:44 PM, Andrew Haley <aph@redhat.com> wrote:
>
> Pavan R wrote:
> > Hi,
> >
> > We find our application dumps core on Suse 10 SP1 that has
> > libgcc-4.1.2_20070115-0.11 shipped, with the top of the stack as :
> >
> > Program terminated with signal 11, Segmentation fault.
> > #0 0xf7aca09c in memcpy () from /lib/libc.so.6
> > (gdb) bt
> > #0 0xf7aca09c in memcpy () from /lib/libc.so.6
> > #1 0x08050a84 in uw_install_context_1 ()
> > #2 0x08050efc in _Unwind_Resume ()
> >
> > The findings are that, by having /lib/libgcc_s.so.1 replaced with the
> > version : libgcc42-4.2.1_20070724-17 we
> > got around with the issue.
> >
> > Can anyone plz point us to any related bugs fixed in the mentioned
> > libgcc version related to _Unwind_Resume.
>
> Did you compile your application on the same machine on which it was
> run?
>
> Andrew.
>