From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: segfault on 32bit cygwin snapshot
Date: Tue, 2 Mar 2021 16:48:45 +0100 [thread overview]
Message-ID: <YD5eXbxBWbUUSwcM@calimero.vinschen.de> (raw)
In-Reply-To: <20210302200308.62db4fe01f78fb35a538784f@nifty.ne.jp>
On Mar 2 20:03, Takashi Yano via Cygwin wrote:
> On Mon, 1 Mar 2021 21:25:42 +0900
> Takashi Yano wrote:
> > On Mon, 1 Mar 2021 09:55:46 +0900
> > Takashi Yano wrote:
> > > On Sun, 28 Feb 2021 19:48:28 +0100
> > > Marco Atzeri wrote:
> > > > On 20.02.2021 23:29, Takashi Yano wrote:
> > > > > On Sat, 20 Feb 2021 22:01:38 +0100
> > > > > Marco Atzeri wrote:
> > > > >> MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10)
> > > > >>
> > > > >> now fails at startup with
> > > > >>
> > > > >> Exception: STATUS_ACCESS_VIOLATION at eip=61083736
> > > > >
> > > > > Thanks for the report. I found the cause of this issue.
> > > > > I will submit a patch to fix it.
> > > > >
> > > >
> > > > mc is now fine with 2021-02-22
> > > >
> > > > but I found another issue
> > > >
> > > > $ /usr/bin/lilypond
> > > > GNU LilyPond 2.20.0
> > > > Segmentation fault (core dumped)
> > > >
> > > > on 3.1.7 it works fine
> > >
> > > I found this problem causes after the commit:
> > >
> > > commit 532b91d24e9496c7988b2b1dda7fc0e8b161f782
> > > Author: Corinna Vinschen <corinna@vinschen.de>
> > > Date: Mon Dec 14 12:29:23 2020 +0100
> > >
> > > Cygwin: Make sure newer apps get uname_x even when loading uname dynamically
> > >
> > > if an application built after API version 334 loads uname dynamically,
> > > it actually gets the old uname, rather than the new uname_x. Fix this by
> > > checking the apps API version in uname and call uname_x instead, if it's
> > > a newer app.
> > >
> > > Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
> > >
> > > Reverting this commit solves the issue.
> > >
> > > Corinna, could you please have a look?
> >
> > The following check code does not work as expected if
> > newly build exe file is linked with old dll which calls
> > uname() as in this case.
> >
> > if (CYGWIN_VERSION_CHECK_FOR_UNAME_X)
> > return uname_x (in_name);
> >
> > Any idea?
>
> Ping Corinna?
I have no idea how we could fix that, other than by rebuilding the DLLs
which call uname, too. We can't check the Cygwin build of all DLLs an
executable is linked to.
Corinna
next prev parent reply other threads:[~2021-03-02 15:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 21:01 Marco Atzeri
2021-02-20 22:29 ` Takashi Yano
2021-02-28 18:48 ` Marco Atzeri
2021-03-01 0:55 ` Takashi Yano
2021-03-01 8:41 ` Takashi Yano
2021-03-01 11:26 ` Takashi Yano
2021-03-01 12:17 ` marco atzeri
2021-03-01 12:25 ` Takashi Yano
2021-03-02 11:03 ` Takashi Yano
2021-03-02 15:48 ` Corinna Vinschen [this message]
2021-03-03 9:56 ` Takashi Yano
2021-03-03 11:00 ` Corinna Vinschen
2021-03-04 9:05 ` Mark Geisert
2021-03-04 16:11 ` Corinna Vinschen
2021-03-05 9:18 ` Mark Geisert
2021-03-05 14:37 ` Corinna Vinschen
2021-03-04 9:05 ` Takashi Yano
2021-03-04 11:11 ` marco atzeri
2021-03-04 11:50 ` Takashi Yano
2021-03-04 15:17 ` Ken Brown
2021-03-04 15:54 ` Corinna Vinschen
2021-03-04 20:17 ` Marco Atzeri
2021-03-05 8:09 ` Marco Atzeri
2021-03-05 9:11 ` Mark Geisert
2021-03-05 14:42 ` Corinna Vinschen
2021-03-05 16:30 ` Marco Atzeri
2021-03-06 1:45 ` Takashi Yano
2021-03-06 17:16 ` Ken Brown
2021-03-06 21:38 ` Mark Geisert
2021-03-05 22:55 ` Mark Geisert
2021-03-08 11:07 ` Mark Geisert
2021-03-08 14:01 ` Corinna Vinschen
2021-03-04 15:52 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YD5eXbxBWbUUSwcM@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).