On Feb 7, 2008 11:33 AM, Pavan R <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> Thanks for the response. The question was, how was the libgcc that
> was shipped with suse 10 SP1
> was incompatible with our RHEL3 compiled program , whereas replacing
> the libgcc with a latest one works fine ?
> Are t
Andrew,
Thanks for the response. The question was, how was the libgcc that
was shipped with suse 10 SP1
was incompatible with our RHEL3 compiled program , whereas replacing
the libgcc with a latest one works fine ?
Are there any compat issues dealt in libgcc recent releases ?
At the first c
Pavan R wrote:
Can I get some help on this.
Surely you already have an answer. The libgcc on suse 10 isn't
compatible with your RHEL3-compiled program, so you discovered
the fix was to put a better libgcc in your LD_LIBRARY_PATH.
Since you have found a fix that works, why do you still want
he
Can I get some help on this.
-- Forwarded message --
From: Pavan R <[EMAIL PROTECTED]>
Date: Jan 29, 2008 5:27 PM
Subject: Fwd: _Unwind_Resume on the stack
To: gcc@gcc.gnu.org
No, We have compiled our application on RHEL 3 with libgcc-3.2.3-34.
On Jan 29, 2008 3
No, We have compiled our application on RHEL 3 with libgcc-3.2.3-34.
On Jan 29, 2008 3:44 PM, Andrew Haley <[EMAIL PROTECTED]> 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 a
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/
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 0x08
