public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Johannes Khoshnazar-Thoma <johannes@johannesthoma.com>
To: cygwin@cygwin.com
Subject: Re: cygwin application hangs on closing console
Date: Tue, 23 Apr 2024 11:20:16 +0200	[thread overview]
Message-ID: <b71816f0-633c-4eaf-b9d6-955b10e4866a@johannesthoma.com> (raw)
In-Reply-To: <20240423035104.85352f8a8d821c0f4d569d18@nifty.ne.jp>

Am 22.04.24 um 20:51 schrieb Takashi Yano:
> On Mon, 22 Apr 2024 14:50:51 +0200
> Johannes Khoshnazar-Thoma wrote:
>> Hi cygwin team :)
>>
>> I have found something what may be a cygwin bug. Sometimes
>> (1 out of 1000 times) a drbdadm.exe process (which is part of WinDRBD's
>> user mode programs originally written for Linux) hangs for several
>> days on exiting (closing the console). I got a minidump and analyzed
>> the dump with gdb (the minidump enabled version at https://github.com/ssbssa/gdb)
>>
>> I have to note that the application (drbdadm.exe) is run from a
>> Windows Service. Furthermore it is not a full cygwin installation
>> however the cygwin1.dll (3.4.10-1) is in the $PATH.
>
> Thanks for the report. Could you please test cygwin1.dll 3.5.3-1
> wihch is the latest cygwin release?
>
Thanks for your reply.

Yes, sure, will test it with 3.5.3 as well. Due to round trip times
with the client this may take one or 2 weeks, however.

Just wanted to ask if the 3.4 branch is end of life?

Best regards,

- Johannes

  reply	other threads:[~2024-04-23  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 12:50 Johannes Khoshnazar-Thoma
2024-04-22 18:51 ` Takashi Yano
2024-04-23  9:20   ` Johannes Khoshnazar-Thoma [this message]
2024-04-23 10:26     ` Takashi Yano
2024-05-15 15:37       ` Johannes Khoshnazar-Thoma
2024-05-15 15:48         ` Johannes Khoshnazar-Thoma
2024-05-15 20:24           ` Brian Inglis
2024-05-16  9:14           ` 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=b71816f0-633c-4eaf-b9d6-955b10e4866a@johannesthoma.com \
    --to=johannes@johannesthoma.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).