This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: 64bit: C++ templates
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 23 May 2013 10:46:16 +0200
- Subject: Re: 64bit: C++ templates
- References: <516CDE32 dot 5000206 at users dot sourceforge dot net> <516F5F89 dot 40600 at users dot sourceforge dot net> <518C9018 dot 9030606 at users dot sourceforge dot net> <CAEwic4aPQHUChVWui6h0FctFkHXh3A0zwh1On50cJRE=SV1UeA at mail dot gmail dot com> <CAEwic4ZAy++TifyZR=XZnD_xahM0GOdO-XREvY6ZdKGQRc+ykA at mail dot gmail dot com> <20130516082534 dot GB11933 at calimero dot vinschen dot de> <5199C9DB dot 8040406 at users dot sourceforge dot net> <20130520092614 dot GA31140 at calimero dot vinschen dot de> <20130522081013 dot GA30892 at calimero dot vinschen dot de> <519D1DB1 dot 8020409 at users dot sourceforge dot net>
- Reply-to: cygwin-developers at cygwin dot com
On May 22 14:34, Yaakov (Cygwin/X) wrote:
> On 2013-05-22 03:10, Corinna Vinschen wrote:
> >On May 20 11:26, Corinna Vinschen wrote:
> >>On May 20 01:59, Yaakov (Cygwin/X) wrote:
> >>>On 2013-05-16 03:25, Corinna Vinschen wrote:
> >>>>Some more testing now showed clearly that this problem is related to the
> >>>>high address used as base addresses in the Cygwin toolchain. If you
> >>>>build the harfbuzz DLL not with
> >>>>
> >>>> -Wl,--enable-auto-image-base
> >>>>
> >>>>but instead with a fixed address in the lower 31 bit address area,
> >>>>for instance
> >>>>
> >>>> -Wl,--image-base -Wl,0x7ff00000
> >>>>
> >>>>the problem disappears and you can successfully build the DLL.
> >>>
> >>>This seems to fix harfbuzz wrt gtk2; gtk3 still isn't working, but
> >>>I'm not sure it's related yet.
> >>
> >>Dunno, but more info on that might help my collegues to fix the issue.
> >
> >Any more info here?
>
> No, I haven't had time to look into it.
>
> >>>>Alternatively, you can also workaround this issue by building harfbuzz
> >>>>with the -mcmodel=large option, which doesn't suffer this problem due to
> >>>>the way symbols are only indirectly addressed.
> >>>
> >>>With this, the link succeeded but I got SEGVs in one of the same
> >>>symbols that failed to link previously.
> >
> >Assuming the build worked, how can one reproduce this SEGV?
>
> e.g. running gtk-demo (from the gtk2.0-demo package).
And what kind of action will trigger the SEGV?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat