From: marco atzeri <marco.atzeri@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: segfault on 32bit cygwin snapshot
Date: Mon, 1 Mar 2021 13:17:48 +0100 [thread overview]
Message-ID: <CAB8Xom_rvo4bf4QAVz2Gc55i9BFuCmj-BF4F6vzUrpTQ=sAPiA@mail.gmail.com> (raw)
In-Reply-To: <20210301202622.1f880e6392f49f2a67c50ddc@nifty.ne.jp>
On Mon, Mar 1, 2021 at 12:59 PM Takashi Yano via Cygwin wrote:
>
> On Mon, 1 Mar 2021 17:41:57 +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:
> > > > 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?
> >
> > I looked into this deeper a bit.
> >
> > Perhaps, lilypond passes old small sized utsname structure to
> > uname() via old cygguile-17.dll (built on Apr. 2017). This seems
> > to cause stack destruction.
>
> So, I guess rebuilding and replacing cygguile-17.dll will solve
> the issue. However, I am not sure whehter the new binary works
> with cygwin 3.1.7.
>
> --
> Takashi Yano
I can rebuild cygguile-17.dll and see if work also with 3.1.7
but I wonder which other DLL's will suffer the same problem
next prev parent reply other threads:[~2021-03-01 12:18 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 [this message]
2021-03-01 12:25 ` Takashi Yano
2021-03-02 11:03 ` Takashi Yano
2021-03-02 15:48 ` Corinna Vinschen
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='CAB8Xom_rvo4bf4QAVz2Gc55i9BFuCmj-BF4F6vzUrpTQ=sAPiA@mail.gmail.com' \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).