This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Core dump on 32-bit Cygwin if program calls dlopen


On Jul 17 16:31, Jon TURNEY wrote:
> On 17/07/2014 08:37, Corinna Vinschen wrote:
> >On Jul 17 06:02, JonY wrote:
> >>On 7/16/2014 15:02, Corinna Vinschen wrote:
> >>>On Jul 15 16:39, Corinna Vinschen wrote:
> >>>>On Jul 15 21:55, JonY wrote:
> >>>>>On 7/15/2014 21:08, Corinna Vinschen wrote:
> >>>>>>>
> >>>>>>>FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.
> >>>>>>
> >>>>>>JonY, do you have a chance to have a look into this issue?
> >>>>>
> >>>>>Sorry, I have been busy these few weeks, but I am well aware that there
> >>>>>is a problem with one of the libgcc changes, but has yet to investigate it.
> >>>>>
> >>>>>I believe Jon Turney has looked into it somewhat.
> 
> I think this is the same or a similar problem to the one I reported at [1].
> I also created a gcc bug [2], with a suggested patch.
> 
> >>>>Sounds good.  Thanks in advance.
> >>>
> >>>Yesterday I asked my collegues to take a stab at the issue and one of
> >>>them, DJ Delorie, came up with a libgcc patch already.  It hasn't been
> >>>sent upstream yet.  Can we give it a try, perhaps by creating a new
> >>>libgcc DLL, please?
> >>
> >>Thanks, I'll get to it this weekend, should I make the new gcc an
> >>experimental version? Or is just the libgcc binary required?
> >
> >It's the libgcc DLL which gives us grief, so a new libgcc package is
> >sufficent, afaics.  We should check if this DLL fixes the problem and
> >then make it "curr" soon, I think.
> 
> I briefly tested this other patch with my test case from the mail above, and
> it doesn't seem to help.
> 
> On 15/07/2014 15:45, Jan Nijtmans wrote:
> > Is this essentially the same problem as described here?
> >
> >      <http://gcc.gnu.org/ml/gcc/2013-05/msg00180.html>
> 
> No, I think it is an unforeseen consequence of the patch [3] to fix that bug
> [4], which I believe is present in 4.8.3-1, introducing a new problem when
> an executable which doesn't depend on libgcc dlopen()s a dll which does.
> 
> [1] https://cygwin.com/ml/cygwin/2014-07/msg00083.html
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61752
> [3] https://sourceware.org/ml/cygwin/2013-07/msg00528.html
> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57982

I asked DJ to take another look, but I guess ultimately we need the
attention of one of the GCC Windows maintainers.  Kai Tietz seems to be
unavailable right now, unfortunately.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpC1jvGK86FL.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]