This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Fwd: _Unwind_Resume on the stack
- From: "Pavan R" <pavanrallabhandis at gmail dot com>
- To: "Andrew Haley" <aph at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 7 Feb 2008 16:03:27 +0530
- Subject: Re: Fwd: _Unwind_Resume on the stack
- References: <44a226ec0801290027x48a79a5v10e646788d0bbc20@mail.gmail.com> <479EFC72.5050904@redhat.com> <44a226ec0801290234va0304dbt2977613a5fc45fb5@mail.gmail.com> <44a226ec0801290357q31e20faahe09733dcab3f0191@mail.gmail.com> <44a226ec0802060608g141f33f0ofc16c54c8842a658@mail.gmail.com> <47AAD666.4090507@redhat.com>
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 case , we werent in favour of replacing libgcc on our
machines. Now then we figured out a latest version of libgcc
helps in resolving the case , we want to know are there any specific
fixes went in the releases of libgcc that address our issue.
Thanks,
- Pavan.
On Feb 7, 2008 3:29 PM, Andrew Haley <aph@redhat.com> wrote:
> 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
> help?
>
> Andrew.
>
>