From: Marco Atzeri <marco.atzeri@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Subject: Re: segfault on 32bit cygwin snapshot
Date: Sun, 28 Feb 2021 19:48:28 +0100 [thread overview]
Message-ID: <7480c946-8e02-aba2-c06f-6b39f630699f@gmail.com> (raw)
In-Reply-To: <20210221072954.db2dcbd523ed366e4dfcb0d0@nifty.ne.jp>
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
stackdump is not very informative
Exception: STATUS_ACCESS_VIOLATION at eip=00000000
eax=FFCD8870 ebx=000no000 ecx=00000000 edx=FF390820 esi=00000000
edi=00000000
ebp=00B4C1D8 esp=00B4C120 program=D:\cygwin32\bin\lilypond.exe, pid
44036, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
00B4C1D8 00000000 (00000000, 00000000, 00000000, 00000000)
End of stack trace
next prev parent reply other threads:[~2021-02-28 18: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 [this message]
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
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=7480c946-8e02-aba2-c06f-6b39f630699f@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).