From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: segfault on 32bit cygwin snapshot
Date: Thu, 4 Mar 2021 10:17:03 -0500 [thread overview]
Message-ID: <b7338aaa-c1e1-1816-35f8-666c2f6ac618@cornell.edu> (raw)
In-Reply-To: <20210304205000.4ac34afe1a8b767ea2986291@nifty.ne.jp>
On 3/4/2021 6:50 AM, Takashi Yano via Cygwin wrote:
> On Thu, 4 Mar 2021 12:11:11 +0100
> marco atzeri wrote:
>> I have no problem to patch Python to solve the issue,
>> but I have not seen evidence of the dlsym mechanism .
>> But of course I an NOT and expert in this field.
>>
>> If someone looking to the code can give me some hints,
>> I will appreciate
>
> I am also not sure where the dlsym() is used in python.
> At least, os.uname() works in python 3.8.7 and 2.7.18 in my
> environment even without that snippet. It seems that os.uname()
> does not use dlsym(). Do I overlook something?
This all started because Mark reported a problem building python 3.8.3:
https://cygwin.com/pipermail/cygwin-apps/2020-December/040765.html
https://cygwin.com/pipermail/cygwin-developers/2020-December/012019.html
It's strange that Marco never bumped into the problem.
Ken
next prev parent reply other threads:[~2021-03-04 15:17 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
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 [this message]
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=b7338aaa-c1e1-1816-35f8-666c2f6ac618@cornell.edu \
--to=kbrown@cornell.edu \
--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).