public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: python3 3.9.18-1 hanging
Date: Sat, 24 Feb 2024 07:42:58 +0100	[thread overview]
Message-ID: <c49d3c8d-27d4-4001-b34d-1d3e589e7a46@gmail.com> (raw)
In-Reply-To: <b655c595-a73a-40c4-8b9a-2c0bfc0b2813@gmail.com>

On 20/02/2024 04:46, Marco Atzeri wrote:
> On 20/02/2024 03:46, Takashi Yano via Cygwin wrote:

>>
>> I hit probably the same issue while building pango1.0 1.51.2-1
>> with python39 3.9.18-2 (Test) installed.
>>
>> Several python3.9 processes are stalled and some of them cannot
>> be terminated even with kill -9.
>>
>> Attaching gdb to them shows SIGSEGV in the thread whose stack
>> is corrupted. The program counter is 0 as follows. Null function
>> pointer dereference?
>>
>> Thread 12 "python3.9" received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 19184.0x18ac]
>> 0x0000000000000000 in ?? ()
>>
>> Another thread seems to stop in exit_thread() (winsup/cygwin/sigproc.cc).
>> It may be due to SEGV.
>>
>> Downgrading it to 3.9.16-1 solves the issue.
>>
> 
> The problem seems to be somewhere between 3.16 and 3.17
> 
> it is also the upstream transition were several patches are
> not used anymore, so it seems the new inside path has some
> hidden consequence for Cygwin
> 

to avoid anymore ME TOO test failure, I removed python 3.18-1 and -2
completely

Regards
Marco




      reply	other threads:[~2024-02-24  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  9:22 Andrew Murray
2024-01-30 10:18 ` Marco Atzeri
2024-01-30 12:13   ` ggl329
2024-01-30 13:23     ` Marco Atzeri
2024-01-31 16:36   ` Eliah Kagan
2024-01-31 17:17     ` Marco Atzeri
2024-02-20  2:46   ` Takashi Yano
2024-02-20  3:46     ` Marco Atzeri
2024-02-24  6:42       ` Marco Atzeri [this message]

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=c49d3c8d-27d4-4001-b34d-1d3e589e7a46@gmail.com \
    --to=marco.atzeri@gmail.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).