Re: wrap around problem for "double"?

2009-12-19 Thread Dave Korn
Phan, Linh H (343H) wrote: > Hi, > > I was wondering why when "double" is assigned into a "short int" in cygwin > 1.7, it doesn't wrap around correctly, A double is a floating-point type, not an integer. Your program is incorrect; it invokes undefined behaviour per n1256#6.3.1.4.1: > When a

wrap around problem for "double"?

2009-12-19 Thread Phan, Linh H (343H)
Hi, I was wondering why when "double" is assigned into a "short int" in cygwin 1.7, it doesn't wrap around correctly, eg: main () { short int x; int y = -63757; double y2 = -63757; x = y; // wraps around correctly going from int to short int printf("%d (should be 1779)\n",x); x =

RE: rsync hangs on big transfer Debian 5.0.3 pulling from WinXP SP3/Cygwin 1.5.25

2009-12-19 Thread David Christensen
Cygwin: I received three copies of my message from each of three lists. If everyone else receives three copies, I apologize for the extraneous copies. :-( Does anybody know why, and how to prevent such? TIA, David -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: rsync hangs on big transfer Debian 5.0.3 pulling from WinXP SP3/ Cygwin 1.5.25

2009-12-19 Thread David Christensen
Debian Users, Cygwin, & Rsync: I'm having trouble with rsync invoked on Debian 5.0.3 pulling files from Windows XP SP3/ Cygwin 1.5.25. I posted to the Debian User and Cygwin mailing lists [1] and thought I was done two days ago, but I wasn't -- after several hours of use of the Windows machine, r

Re: perl: XML-Parser missing in 5.10.1-1

2009-12-19 Thread Reini Urban
2009/12/18 Reini Urban: > 2009/12/16 Yaakov (Cygwin/X): >> XML-Parser appears to have gone missing in perl-5.10.1-1.  This module is >> essential for a number of purposes, including intltool (a GNOME build tool). >>  Please let me know ASAP if you are planning on restoring this in the VERY >> near

Re: 2nd occurrence of signal not being handled?

2009-12-19 Thread Christopher Faylor
On Sat, Dec 19, 2009 at 05:23:42AM +, Mark Geisert wrote: >I'm trying to get a larger application working but have an issue with >signal handling. I've boiled the issue down to the STC below. It >causes two access violations, only the first of which gets handled by >the SIGSEGV signal handler

Re: 2nd occurrence of signal not being handled?

2009-12-19 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Mark Geisert on 12/18/2009 10:23 PM: > Or maybe there's some subtle > mistake in my use of the signal functions. Any advice would be appreciated. > > ..mark > > #include > #include > #include > > volatile intstep = 0; > sigjmp_b