X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:date:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=n8Yu 92yTS5J0m/DRE72XPoyb8j4+YgZAAtKcgoMJrsbWL9v8Dz31RVSOp/n3H3PSc8pF p8pt7LMBVGzzJ3pPQehTwvVDRMnNSpAbs80veXZhDFnR7LTBR7/GoFPW5T4NM7uG 51xJAzJdWVcxhE34RVzChPJAc0vdO1V13+iF8Cw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:date:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=g02WGRvbe6 wchxhOhPIMYSFoyUY=; b=OjA65zfROAhLvQbhxYvFFwyQ/k8O/j9GzUbyVxBZPV 1Yqu083uY19dMwmhEwZAo8pCx8U4vM2iDzjSfqD0Wb6gAy2EReSQIR0AoLlhtpCM Muc5rFfgYY5rufqlDqglbYZJm6Zfagj6asQ8vCC9Au305GcAPjP4OK/OZhpEJ9lC I= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-la0-f54.google.com X-Received: by 10.152.203.204 with SMTP id ks12mr13116364lac.65.1410344554812; Wed, 10 Sep 2014 03:22:34 -0700 (PDT) From: Alexey Shumkin X-Google-Original-From: Alexey Shumkin Date: Wed, 10 Sep 2014 14:22:27 +0400 To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , Marco Atzeri Subject: Re: mktime call hangs on Cygwin 1.7.30, Windows 7 32 bit Message-ID: <20140910102227.GA21313@ashu.dyn1.rarus.ru> Mail-Followup-To: Alexey Shumkin , cygwin AT cygwin DOT com, Corinna Vinschen , Marco Atzeri References: <20140902111045 DOT GA5860 AT ashu-win7> <5405AACD DOT 5050600 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline In-Reply-To: <5405AACD.5050600@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes On Tue, Sep 02, 2014 at 01:32:29PM +0200, Marco Atzeri wrote: > On 02/09/2014 13:10, Alexey Shumkin wrote: > >Prelude. > >I use "self-compiled" Git (v2.x) on Cygwin (v1.7.30). > >Sometimes Git v2.0.4 hung while performing > > git prune --expire 2.weeks.ago > > > >I have investigated while debugging that `mktime` call hung. > >But that was an avoidable bug (skip prune - and all is ok). So, I've not > >reported it. > > > >But after updating Git to v2.1.0 > > git commit --amend -C HEAD --date='' > >hangs, too. And now it is the often used operation by me. > >So, I've made a simple example (copied from Git sources) to reproduce > >the error. > > > >$ cat cygwin-mktime-bug.c > >#include > >#include > >#include > > > >int main(int argc, char **argv) > >{ > > struct tm tm; > > > > memset(&tm, 0, sizeof(tm)); > > tm.tm_year = -1; > > tm.tm_mon = -1; > > tm.tm_mday = -1; > > tm.tm_isdst = -1; > > tm.tm_hour = -1; > > tm.tm_min = -1; > > tm.tm_sec = -1; > > > > printf("Working...\n"); > > time_t temp_time = mktime(&tm); > > printf("Worked"); > - printf("Worked"); > - printf("Worked\n"); > >} > > > >$ gcc cygwin-mktime-bug.c -o cygwin-mktime-bug -I/usr/include -g > >$ ./cygwin-mktime-bug.exe > >Working... > > > no issue on my side. I've tested on another machines with Cygwin v1.7.11 and v1.7.25. And it worked. That`s Ok. Also, I've run ./cygwin-mktime-bug.exe in CMD, and SUPRISINGLY it worked, but when I run the SAME `cygwin-mktime-bug.exe` in `bash -l -i` it does not! Ha-ha! After I've wrote text above, I've tested run `cygwin-mktime-bug.exe` in `bash`, `bash -i`, `bash -l` AND(!) it worked well in first TWO cases (`bash` & `bash -i`), and DOES NOT in `bash -l`. How can it be? 8-O > > $ LIMIT=1000 > $ for ((a=1 ; a <= LIMIT ; a++ )); do ./cygwin-mktime-bug.exe ; done > > Working... > Worked > ... > Working... > Worked > $ > > > > > >So, there is a question: how to fix it? > >Nota bene: I do not want to use Cygwin x64 (there were no exim when I've tested it). > > 32 bit here. > > $ uname -svr > CYGWIN_NT-6.1-WOW64 1.7.32(0.274/5/3) 2014-08-13 23:03 > > please update to 1.7.32 and than follows: > https://cygwin.com/problems.html > > Regards > Marco > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple