libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libunwind] Linking with libunwind.a using the Intel compiler


From: David Mosberger
Subject: Re: [libunwind] Linking with libunwind.a using the Intel compiler
Date: Thu, 6 Jan 2005 10:50:14 -0800

>>>>> On Thu, 30 Dec 2004 16:08:16 -0600, Jeremy Suurkivi <address@hidden> said:

  Jeremy> This seems to be a reasonable solution but I'm still a
  Jeremy> little nervous using it.  It seems that the Intel compiler
  Jeremy> statically links in its own unwind library (libunwind.so.4
  Jeremy> in this case) and it seems there is a symbol clash with
  Jeremy> _Unwind_Resume.  Is it safe to substitute _Unwind_Resume
  Jeremy> from one library into the other?  Or to have both of these
  Jeremy> libraries linked in at the same time?

In theory, the two libunwind's should be compatible as far as the
_Unwind_*() API is concerned---that's defined by the C++ ABI.  In
practice, since everybody used to ship their own libunwind, I'm not
surprised to hear that there are some glitches with older compilers.

        --david

reply via email to

[Prev in Thread] Current Thread [Next in Thread]