This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [RFA] pei386 dll: auto-import patch
- To: Paul Sokolovsky <Paul dot Sokolovsky at technologist dot com>, Charles Wilson <cwilson at ece dot gatech dot edu>, Robert Collins <robert dot collins at itdomain dot com dot au>
- Subject: Re: [RFA] pei386 dll: auto-import patch
- From: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>
- Date: Sun, 5 Aug 2001 09:27:14 +1000 (EST)
- Cc: binutils at sources dot redhat dot com
--- Paul Sokolovsky <Paul.Sokolovsky@technologist.com> wrote: >
Gentlemen,
>
> 4. I have no idea what may cause problems with elaborated C++ stuff
> (containing templates, etc.). The first thing to check is place where
> segfault happens - in OS linker or in app startup. If the latter is
> the case, then, as Danny Smith points out, it may be an issue with
> C++
> dlls at all, and not just with auto-import.
The problems I have seen are in app startup, or sometime later, when an
dll-imported template class instantiation uses a helper template
object that is instantiated outside of the dll, rather than it's own
"specialisation" within the dll. The issue is what can be exposed in
headers for dll version compared to static version. It is not an an
--enable-auto-import issue, IMO. It can be confused with
--enable-auto-import, which was my initial reaction. I was wrong. The
__MYLIB_USE_DLL type of macros can do more than just switch
import/export attributes Now that I see what's going on I can
reproduce the same "bug" using the old ld and __attribute__(dllimport).
Danny
>
>
> Hope this helps a bit,
>
>
> --
> Paul Sokolovsky, IT Specialist
> http://www.brainbench.com/transcript.jsp?pid=11135
>
>
_____________________________________________________________________________
http://messenger.yahoo.com.au - Yahoo! Messenger
- Voice chat, mail alerts, stock quotes and favourite news and lots more!