RE: BUG: ualarm(0,0) not clearing ualarms
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Robb, Sam > Sent: Tuesday, February 14, 2006 10:09 AM > To: cygwin@cygwin.com > Subject: RE: BUG: ualarm(0,0) not clearing ualarms > > Gary R. Van Sickle wrote: > > I get the same can't-duplicate as Chris does, on 'uname -a'= > > > > CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 > > i686 Cygwin > > > > I don't have any of this stuff in $CYGWIN, might be worth a try to > > ditch it: > > > > " > > CYGWIN = 'server ntsec forkchunk:32768' > > " > > Chris, Gary, et al, > > I'm able to reproduce this on my machine, but only when I'm > running it under rxvt. If I run it from cmd.exe or within a > standard cygwin bash shell, then it completes without the > '-- BOGUS ALARM --' warnings. > > $ uname -a > CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > > $ gcc -o ua-test ua-test.c > > $ ./ua-test.exe > First ualarm - one shot > Second ualarm - one shot > Last ualarm - repeats 3 times > Clearing ualarm > Sleeping > --- BOGUS ALARM --- > --- BOGUS ALARM --- > Done > > -Samrobb Rxvt here too, but no problems. WinXPSP2+EveryPossibleUpdate btw. -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
On Tue, Feb 14, 2006 at 01:05:09PM -0500, Reid Thompson wrote: >>> I'm able to reproduce this on my machine, but only when I'm >>>running it under rxvt. If I run it from cmd.exe or within a >>>standard cygwin bash shell, then it completes without the >>>'-- BOGUS ALARM --' warnings. >>> >>> $ uname -a >>> CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin >>> >>> $ gcc -o ua-test ua-test.c >>> >>> $ ./ua-test.exe >>> First ualarm - one shot >>> Second ualarm - one shot >>> Last ualarm - repeats 3 times >>> Clearing ualarm >>> Sleeping >>> --- BOGUS ALARM --- >>> --- BOGUS ALARM --- >>> Done >>> >> >>It behaves the same for me no matter where I run it. I even increased the >>final sleep time in case the program was exiting before the bogus alarm >>was tripped. > >my previous test case was run under rxvt as well, with no BOGUS ALARM's >noted. Ditto, on both W2K and XP. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
Robb, Sam wrote: From: "Robb, Sam" I'm able to reproduce this on my machine, but only when I'm running it under rxvt. If I run it from cmd.exe or within a standard cygwin bash shell, then it completes without the '-- BOGUS ALARM --' warnings. $ uname -a CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin $ gcc -o ua-test ua-test.c $ ./ua-test.exe First ualarm - one shot Second ualarm - one shot Last ualarm - repeats 3 times Clearing ualarm Sleeping --- BOGUS ALARM --- --- BOGUS ALARM --- Done I'm the original poster of this bug report. I usually run in an rxvt window, which is where I see the bug. I tried a dos window, and the bug did not occur. Further, it occurs on my Win2K box, but not on my WinXP box. Jerry, I've cc'd the cygwin list on this reply since the difference (Win2K vs. WinXP) may be significant. I'm also running cygwin under Win2K. It may be that others who have not seen this error are also running under XP as well. -Samrobb my system is XP/SP2. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
I'm able to reproduce this on my machine, but only when I'm running it under rxvt. If I run it from cmd.exe or within a standard cygwin bash shell, then it completes without the '-- BOGUS ALARM --' warnings. $ uname -a CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin $ gcc -o ua-test ua-test.c $ ./ua-test.exe First ualarm - one shot Second ualarm - one shot Last ualarm - repeats 3 times Clearing ualarm Sleeping --- BOGUS ALARM --- --- BOGUS ALARM --- Done It behaves the same for me no matter where I run it. I even increased the final sleep time in case the program was exiting before the bogus alarm was tripped. cgf my previous test case was run under rxvt as well, with no BOGUS ALARM's noted. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: BUG: ualarm(0,0) not clearing ualarms
> > From: "Robb, Sam" > > I'm able to reproduce this on my machine, but only when I'm > > running it under rxvt. If I run it from cmd.exe or within a > > standard cygwin bash shell, then it completes without the > > '-- BOGUS ALARM --' warnings. > > > > $ uname -a > > CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > > > > $ gcc -o ua-test ua-test.c > > > > $ ./ua-test.exe > > First ualarm - one shot > > Second ualarm - one shot > > Last ualarm - repeats 3 times > > Clearing ualarm > > Sleeping > > --- BOGUS ALARM --- > > --- BOGUS ALARM --- > > Done > > I'm the original poster of this bug report. > I usually run in an rxvt window, which is where I see the bug. > I tried a dos window, and the bug did not occur. > Further, it occurs on my Win2K box, but not on my WinXP box. Jerry, I've cc'd the cygwin list on this reply since the difference (Win2K vs. WinXP) may be significant. I'm also running cygwin under Win2K. It may be that others who have not seen this error are also running under XP as well. -Samrobb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
On Tue, Feb 14, 2006 at 11:08:52AM -0500, Robb, Sam wrote: >Gary R. Van Sickle wrote: >> I get the same can't-duplicate as Chris does, on 'uname -a'= >> >> CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 >> i686 Cygwin >> >> I don't have any of this stuff in $CYGWIN, might be worth a >> try to ditch it: >> >> " >> CYGWIN = 'server ntsec forkchunk:32768' >> " > >Chris, Gary, et al, > > I'm able to reproduce this on my machine, but only when I'm >running it under rxvt. If I run it from cmd.exe or within a >standard cygwin bash shell, then it completes without the >'-- BOGUS ALARM --' warnings. > > $ uname -a > CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > > $ gcc -o ua-test ua-test.c > > $ ./ua-test.exe > First ualarm - one shot > Second ualarm - one shot > Last ualarm - repeats 3 times > Clearing ualarm > Sleeping > --- BOGUS ALARM --- > --- BOGUS ALARM --- > Done It behaves the same for me no matter where I run it. I even increased the final sleep time in case the program was exiting before the bogus alarm was tripped. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: BUG: ualarm(0,0) not clearing ualarms
Gary R. Van Sickle wrote: > I get the same can't-duplicate as Chris does, on 'uname -a'= > > CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 > i686 Cygwin > > I don't have any of this stuff in $CYGWIN, might be worth a > try to ditch it: > > " > CYGWIN = 'server ntsec forkchunk:32768' > " Chris, Gary, et al, I'm able to reproduce this on my machine, but only when I'm running it under rxvt. If I run it from cmd.exe or within a standard cygwin bash shell, then it completes without the '-- BOGUS ALARM --' warnings. $ uname -a CYGWIN_NT-5.0 claus 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin $ gcc -o ua-test ua-test.c $ ./ua-test.exe First ualarm - one shot Second ualarm - one shot Last ualarm - repeats 3 times Clearing ualarm Sleeping --- BOGUS ALARM --- --- BOGUS ALARM --- Done -Samrobb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
Gary R. Van Sickle wrote: [snip] I get the same can't-duplicate as Chris does, on 'uname -a'= CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 i686 Cygwin I don't have any of this stuff in $CYGWIN, might be worth a try to ditch it: " CYGWIN = 'server ntsec forkchunk:32768' " Btw, I have a hyperthreaded machine running at 3.06G with 1G of RAM. I wouldn't expect that to make a difference in this case, though. I can't see how this could be a N-processor race-related bug. cgf Hyperthreding P4 3.4GHz "X-Treme Edition" (more cache?), 1Gig RAM. Maybe this is the one bug that HT actually masks instead of reveals. ;-) AMD Athlon XP2500+ 1.83GHZ 512MB RAM. CYGWIN_NT-5.1 cyberhome 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin $ ./ualarm First ualarm - one shot Second ualarm - one shot Last ualarm - repeats 3 times Clearing ualarm Sleeping Done -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: BUG: ualarm(0,0) not clearing ualarms
[snip] > >I get the same can't-duplicate as Chris does, on 'uname -a'= > > > >CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 > i686 Cygwin > > > >I don't have any of this stuff in $CYGWIN, might be worth a > try to ditch it: > > > >" > >CYGWIN = 'server ntsec forkchunk:32768' > >" > > Btw, I have a hyperthreaded machine running at 3.06G with 1G > of RAM. I wouldn't expect that to make a difference in this > case, though. I can't see how this could be a N-processor > race-related bug. > > cgf Hyperthreding P4 3.4GHz "X-Treme Edition" (more cache?), 1Gig RAM. Maybe this is the one bug that HT actually masks instead of reveals. ;-) -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
On Mon, Feb 13, 2006 at 07:33:26PM -0600, Gary R. Van Sickle wrote: >> On Behalf Of Jerry D. Hedden >> Sent: Monday, February 13, 2006 1:58 PM >> Subject: RE: BUG: ualarm(0,0) not clearing ualarms >> >> > Original Message >> > From: Christopher Faylor >> > >> > Thanks for the test case but I don't see any difference in operation >> > between cygwin and linux when I run it: >> >> I know that Perl version of the bug occurred on both my work computer >> (Win2K) and home computer (WinXP) both using the lastest Cygwin DLL. >> The C code I sent, produced the bug on my work computer. >> I'll try my home computer this evening. > >I get the same can't-duplicate as Chris does, on 'uname -a'= > >CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 i686 Cygwin > >I don't have any of this stuff in $CYGWIN, might be worth a try to ditch it: > >" >CYGWIN = 'server ntsec forkchunk:32768' >" Btw, I have a hyperthreaded machine running at 3.06G with 1G of RAM. I wouldn't expect that to make a difference in this case, though. I can't see how this could be a N-processor race-related bug. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: BUG: ualarm(0,0) not clearing ualarms
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jerry D. Hedden > Sent: Monday, February 13, 2006 1:58 PM > To: cygwin@cygwin.com > Subject: RE: BUG: ualarm(0,0) not clearing ualarms > > > Original Message > > From: Christopher Faylor <[EMAIL PROTECTED]> > > > > Thanks for the test case but I don't see any difference in > operation > > between cygwin and linux when I run it: > > I know that Perl version of the bug occurred on both my work computer > (Win2K) and home computer (WinXP) both using the lastest Cygwin DLL. > The C code I sent, produced the bug on my work computer. > I'll try my home computer this evening. I get the same can't-duplicate as Chris does, on 'uname -a'= CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.153/4/2) 20060209 14:37:47 i686 Cygwin I don't have any of this stuff in $CYGWIN, might be worth a try to ditch it: " CYGWIN = 'server ntsec forkchunk:32768' " -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BUG: ualarm(0,0) not clearing ualarms
On Mon, Feb 13, 2006 at 12:58:14PM -0700, Jerry D. Hedden wrote: > From: Christopher Faylor >> >>Thanks for the test case but I don't see any difference in operation >>between cygwin and linux when I run it: > >I know that Perl version of the bug occurred on both my work computer >(Win2K) and home computer (WinXP) both using the lastest Cygwin DLL. I'm not really interested in the Perl version of the bug. I thought that the test case which you forwarded demonstrated the problem. >The C code I sent, produced the bug on my work computer. I'll try my >home computer this evening. Is it possible that something in my >environment is the problem? I don't know what it would be, if so. Btw, please don't use raw email addresses in the body of your messages and please *attach* the cygcheck output. Don't just include it inline in your message. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: BUG: ualarm(0,0) not clearing ualarms
> Original Message > From: Christopher Faylor <[EMAIL PROTECTED]> > > Thanks for the test case but I don't see any difference in operation > between cygwin and linux when I run it: I know that Perl version of the bug occurred on both my work computer (Win2K) and home computer (WinXP) both using the lastest Cygwin DLL. The C code I sent, produced the bug on my work computer. I'll try my home computer this evening. Is it possible that something in my environment is the problem? Cygwin Configuration Diagnostics Current System Time: Mon Feb 13 14:57:12 2006 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path: E:\cygwin\home\jhedden\bin E:\cygwin\usr\local\bin E:\cygwin\bin E:\cygwin\bin E:\cygwin\usr\X11R6\bin C:\Perl\bin\ C:\djgpp\bin C:\Program Files\WiX C:\Program Files\nant-0.85-rc3\bin C:\Program Files\apache-ant-1.6.3\bin C:\j2sdk1.4.2_08\bin C:\Program Files\Documentum\Shared C:\blp\API C:\oracle\ora92\bin C:\Program Files\Oracle\jre\1.3.1\bin C:\Program Files\Oracle\jre\1.1.8\bin C:\WINNT\system32 C:\WINNT C:\WINNT\system32\WBEM C:\Program Files\cvsnt E:\cygwin\usr\local\lib C:\dev-cpp\bin\ .\ Output from E:\cygwin\bin\id.exe (nontsec) UID: 78809(jhedden) GID: 10513(Domain Users) 0(root) 544(Administrators) 545(Users) 10513(Domain Users) Output from E:\cygwin\bin\id.exe (ntsec) UID: 78809(jhedden) GID: 10513(Domain Users) 0(root) 544(Administrators) 545(Users) 10513(Domain Users) SysDir: C:\WINNT\system32 WinDir: C:\WINNT USER = 'jhedden' PWD = '/usr/local/src/perl' CYGWIN = 'server ntsec forkchunk:32768' HOME = '/home/jhedden' MAKE_MODE = 'unix' Use '-r' to scan registry a: fd N/AN/A c: hd NTFS 38161Mb 38% CP CS UN PA FC d: cd N/AN/A e: hd FAT32 114442Mb 14% CPUN EXTERNAL f: net NTFS451498Mb 81% CP CS UN PA FC g: net NTFS 10003Mb 57% CP CS UN PA FC h: net NTFS 10003Mb 57% CP CS UN PA FC v: net NTFS 2753169Mb 69% CP CS UN PAshared y: net NTFS225738Mb 84% CP CS UN PA FC . /cygdrive user binmode,cygdrive E:\cygwin / system binmode C: /c system binmode E:\cygwin/bin /usr/bin system binmode E:\cygwin/lib /usr/lib system binmode E: /x system binmode C:\Documents and Settings\jhedden\My Documents /z system binmode . /cygdrive system binmode,cygdrive Found: E:\cygwin\bin\awk.exe Found: E:\cygwin\bin\bash.exe Found: E:\cygwin\bin\cat.exe Found: E:\cygwin\bin\cp.exe Found: E:\cygwin\bin\cpp.exe Found: C:\dev-cpp\bin\cpp.exe Found: E:\cygwin\bin\crontab.exe Found: E:\cygwin\bin\find.exe Found: E:\cygwin\bin\gcc.exe Found: C:\dev-cpp\bin\gcc.exe Found: C:\dev-cpp\bin\gdb.exe Found: E:\cygwin\bin\grep.exe Found: E:\cygwin\bin\kill.exe Found: E:\cygwin\bin\ld.exe Found: C:\dev-cpp\bin\ld.exe Found: E:\cygwin\bin\ls.exe Found: E:\cygwin\bin\make.exe Found: C:\dev-cpp\bin\make.exe Found: E:\cygwin\bin\mv.exe Found: E:\cygwin\bin\patch.exe Found: E:\cygwin\bin\perl.exe Found: C:\Perl\bin\perl.exe Found: E:\cygwin\bin\rm.exe Found: C:\dev-cpp\bin\rm.exe Found: E:\cygwin\bin\sed.exe Found: C:\djgpp\bin\sed.exe Found: E:\cygwin\bin\ssh.exe Found: E:\cygwin\bin\sh.exe Found: E:\cygwin\bin\tar.exe Found: E:\cygwin\bin\test.exe Not Found: vi Found: E:\cygwin\bin\vim.exe 7k 2003/10/19 E:\cygwin\bin\cygcrypt-0.dll 1210k 2006/02/13 E:\cygwin\bin\cygperl5_8.dll 56k 2005/07/09 E:\cygwin\bin\cygbz2-1.dll 895k 2004/04/28 E:\cygwin\bin\cygdb-4.2.dll 1156k 2004/04/28 E:\cygwin\bin\cygdb_cxx-4.2.dll 19k 2003/03/22 E:\cygwin\bin\cyggdbm.dll 28k 2003/07/20 E:\cygwin\bin\cyggdbm-3.dll 15k 2003/07/20 E:\cygwin\bin\cyggdbm_compat-3.dll 30k 2003/08/11 E:\cygwin\bin\cyggdbm-4.dll 15k 2003/08/11 E:\cygwin\bin\cyggdbm_compat-4.dll 21k 2001/06/20 E:\cygwin\bin\cygintl.dll 22k 2001/12/13 E:\cygwin\bin\cygintl-1.dll 37k 2003/08/10 E:\cygwin\bin\cygintl-2.dll 45k 2001/04/25 E:\cygwin\bin\cygform5.dll 26k 2001/04/25 E:\cygwin\bin\cygmenu5.dll 156k 2001/04/25 E:\cygwin\bin\cygncurses++5.dll 226k 2001/04/25 E:\cygwin\bin\cygncurses5.dll 15k 2001/04/25 E:\cygwin\bin\cygpanel5.dll 35k 2002/01/09 E:\cygwin\bin\cygform6.dll 20k 2002/01/09 E:\cygwin\bin\cygmenu6.dll 175k 2002/01/09 E:\cygwin\bin\cygncurses++6.dll 202k 2002/01/09 E:\cygwin\bin\cygncurses6.dll 12k 2002/01/09 E:\cygwin\bin\cygpanel6.dll 48k 2003/08/09 E:\cygwin\bi
Re: BUG: ualarm(0,0) not clearing ualarms
On Mon, Feb 13, 2006 at 12:18:45PM -0700, Jerry D. Hedden wrote: >I have encounted a bug in Cygwin whereby ualarm(0,0) is not clearing >previously set ualarms. This first cropped up while using Perl, but I >was able to reproduce the bug with the following 'C' program. The gist >is that ualarm() is used several times, and then a final ualarm(0,0) is >executed to clear them. This is followed by a usleep(). The alarm >signal handler shows that 'bogus' alarms are going off during the >usleep(). Without the signal handler, the program would terminate >prematurely due to uncaught SIGALRM. Thanks for the test case but I don't see any difference in operation between cygwin and linux when I run it: % ./ualarm.unix First ualarm - one shot Second ualarm - one shot Last ualarm - repeats 3 times Clearing ualarm Sleeping Done cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
