public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-developers@cygwin.com
Subject: Re: malloc crash
Date: Mon, 25 Oct 2021 09:37:35 -0400	[thread overview]
Message-ID: <56405378-c5d9-cb5c-378f-eea2083b1303@cornell.edu> (raw)
In-Reply-To: <20211025175646.c558458b7ef6eb4b88dc1dc7@nifty.ne.jp>

On 10/25/2021 4:56 AM, Takashi Yano wrote:
> On Sun, 24 Oct 2021 17:46:40 -0400
> Ken Brown wrote:
>> I'm trying to debug the fifo problem reported here:
>>
>>     https://cygwin.com/pipermail/cygwin/2021-October/249635.html
>>
>> To keep my email self-contained, here are the reproduction instructions.  Run
>> the attached script with argument 1000.  The output is supposed to look like this:
>>
>> $ ./fifo_test.sh 1000
>> Creating 1000 fifo readers...
>> Created PID=6503  reading from /tmp/catfifo_0
>> FIFO 0
>> Created PID=6506  reading from /tmp/catfifo_1
>> FIFO 1
>> [...]
>> Created PID=9506  reading from /tmp/catfifo_998
>> FIFO 998
>> Created PID=9509  reading from /tmp/catfifo_999
>> FIFO 999
>>
>> But invariably one of the exec'd cat processes will appear to hang.  (Actually
>> it goes into an infinite loop.)  If you attach gdb to that process and catch it
>> at the right time, you see something like this:
> 
> I noticed that this does not occur with 32-bit cygwin.
> This occurs only with 64-bit cygwin in my environment.

It hadn't occurred to me to test 32-bit, but I just tried, and I can't reproduce 
the problem in that environment either.

> Does malloc behave differently between 32 and 64 bit cygwin?

Ken

  reply	other threads:[~2021-10-25 13:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 21:46 Ken Brown
2021-10-25  8:56 ` Takashi Yano
2021-10-25 13:37   ` Ken Brown [this message]
2021-10-25  8:59 ` Corinna Vinschen
2021-10-25 12:35   ` Ken Brown
2021-10-25 15:39     ` Corinna Vinschen
2021-10-25 21:29       ` Mark Geisert
2021-10-25 22:02         ` Ken Brown
2021-10-25 23:36           ` Mark Geisert
2021-10-26  0:18             ` Takashi Yano
2021-10-26  0:54               ` Mark Geisert
2021-10-26  8:30                 ` Mark Geisert
2021-10-26  8:52                   ` Takashi Yano
2021-10-26  8:59                     ` Mark Geisert
2021-10-26  9:26                       ` Takashi Yano
2021-10-26  9:31                         ` Corinna Vinschen
2021-10-26  9:28                       ` Corinna Vinschen
2021-10-26  9:27                 ` Corinna Vinschen
2021-10-26  9:24           ` Corinna Vinschen
2021-10-26 14:32             ` Ken Brown
2021-10-26 16:03               ` Corinna Vinschen
2021-10-26 16:36                 ` Ken Brown
2021-10-26 16:49                   ` Corinna Vinschen
2021-10-26 17:10                     ` Ken Brown
2021-10-27  0:44                     ` Takashi Yano
2021-10-27  9:01                       ` Corinna Vinschen
2021-10-26 16:44                 ` Takashi Yano

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=56405378-c5d9-cb5c-378f-eea2083b1303@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-developers@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).