X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 17 Feb 2012 18:35:55 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: getitimer() in 1.7.10-1 Message-ID: <20120217173555.GN19092@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Feb 17 17:06, Andrew Mangogna wrote: > After recently updating to 1.7.10-1 of the Cygwin library I have noticed that the invocation of "getitimer()" in my applications is now failing all the time. The following program shows the result: > > #include > #include > #include > #include > > int > main( > int arc, > char **argv) > { > struct itimerval timer ; > > int err = getitimer(ITIMER_REAL, &timer) ; > if (err != 0) { > printf("getitimer failed: %d, \"%s\"(%d)\n", err, strerror(errno), > errno) ; > } > } > [...] > I'm curious if anyone else has seen a problem here. I suspect I'm > doing something wrong, but this has been working for quite some time > in the past and getitimer() is petty mundane stuff. No, you're not doing anything wrong, it's plainly a bug in 1.7.10. A local variable was not correctly used. Thanks for the report and the testcase. This should be fixed in CVS. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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