public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Gruff Hacker <gruffhacker-cyg@yahoo.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: date command hangs sometimes (coreutils 8.26-2) on cygwin 3.1.4 x86-64
Date: Mon, 29 Jun 2020 16:44:19 -0400	[thread overview]
Message-ID: <8b87609b-e757-024f-c08b-ff2bbcaad131@cornell.edu> (raw)
In-Reply-To: <176725751.5473070.1593459690786@mail.yahoo.com>

On 6/29/2020 3:41 PM, Gruff Hacker wrote:
> On Thu Jun 25 11:50:15 GMT 2020, Ken Brown wrote:
> 
> 
>> Can you show us a gdb backtrace of all threads when this happens?  You'll need
>> to install gdb and coreutils-debuginfo.  When date hangs, attach gdb by giving
>> the command
>>
>>     gdb -p <PID>
>>
>> where <PID> is the pid of the hanging date process.  At the gdb prompt, type
>> 'thread apply all bt' and send the output here.
> 
> Thanks Ken.  The gdb output is below.  I did get a symbol mismatch warning so maybe it's not as useful as it could be.  I guess I need to do an update.

Yes, please do a complete update of all your Cygwin packages.

> warning: the debug information found in "/usr/lib/debug//usr/bin/cygwin1.dbg" does not match "/usr/bin/cygwin1.dll" (CRC mismatch).

This probably means that the version of the cygwin package you have installed 
isn't the same as the version of the cygwin-debuginfo package.  As a result, I 
don't think we can do anything with your backtrace.

Ken

      reply	other threads:[~2020-06-29 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <198898587.43311.1588386067082.ref@mail.yahoo.com>
2020-05-02  2:21 ` Gruff Hacker
2020-06-25  0:57   ` Gruff Hacker
2020-06-25 11:50     ` Ken Brown
2020-06-29 19:41     ` Gruff Hacker
2020-06-29 20:44       ` Ken Brown [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=8b87609b-e757-024f-c08b-ff2bbcaad131@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=gruffhacker-cyg@yahoo.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).