Re: mktime call hangs on Cygwin 1.7.30, Windows 7 32 bit
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
Re: vi editing at bash command line: cc command doesn't work
vim 7.4.417-1 OK Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1 Cygwin DLL version info: DLL version: 1.7.32 cc in vi or vim, or gvim Works for me, on 64-bit, without admin rights. PS. Thanks for prompting me to finally notice the mirror I was using was not staying up to date. So that's why updates had stopped. :-) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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
Windows 2008 access to inetsrv directory
I have been puzzling over why a cygwin bash shell cannot access the c:\Windows\System32\inetsrv\backup directory. I have added "Users" and "cyg_server" account to directory permissions. I still cannot cd to or copy from the backup sub-directory. I saw postings regarding accessing certain System32 files failing with 32-bit apps. I tried creating a file system Junction link to the inetsrv directory, still no luck. $ ./cygcheck.exe -V cygcheck (cygwin) 1.7.15 System Checker for Cygwin Copyright (C) 1998 - 2012 Red Hat, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Permissions on dir c:\Windows\System32\inetsrv\backup D:\ois\bin>cacls c:\Windows\System32\inetsrv\backup c:\Windows\System32\inetsrv\backup NT AUTHORITY\SYSTEM:(OI)(CI)F WDIISN03\cyg_server:(OI)(CI)F WDIISN03\nrgo849:(OI)(CI)F WDIISN03\nrgo947:(OI)(CI)F BUILTIN\Administrators:(OI)(CI)F BUILTIN\Users:(OI)(CI)R Any ideas why cygwin/bash.exe cannot access this directory? Scott Tinsley UPGF Midrange Technologies 804-291-4174 scotttins...@ups.com -- 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
Re: vi editing at bash command line: cc command doesn't work
On 9/10/14, 6:36 AM, "Mr. Bob 2001" wrote: >vim 7.4.417-1 OK > >Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1 > >Cygwin DLL version info: >DLL version: 1.7.32 > >cc in vi or vim, or gvim Works for me, on 64-bit, without admin rights. > >PS. Thanks for prompting me to finally notice the mirror I was using was >not staying up to date. So that's why updates had stopped. :-) > > >-- >Sent from my Android device with K-9 Mail. Please excuse my brevity. > >-- >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 > Mr. Bob, I think you misunderstood the original post. The issue is with the vi-edit mode of the bash shell, not gvim or vi. Bob -- 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
Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs
On 9/3/2014 8:41 AM, Sebastien Vauban wrote: Hello, As you can see on http://screencast.com/t/XTTv9DSAC, win32 binaries of Emacs and Cygwin Emacs can't display the white right-pointing triangle [1] coherently for the same fonts: - win32 Emacs always can display it, in all fonts, - Cygwin Emacs can't display it with Consolas, Courier New and Lucida (among others). MWE: --8<---cut here---start->8--- ;; these fonts only display (special?) UTF-8 chars (here: the white ;; right-pointing triangle) in win32 binary of Emacs (modify-all-frames-parameters '((font . "Consolas-10"))) (char-displayable-p ?\u25B7) (modify-all-frames-parameters '((font . "Courier New-9"))) (char-displayable-p ?\u25B7) (modify-all-frames-parameters '((font . "Lucida Console-9"))) (char-displayable-p ?\u25B7) ;; these work for both win32 binary of Emacs + Cygwin Emacs (modify-all-frames-parameters '((font . "DejaVu Sans Mono-9"))) (char-displayable-p ?\u25B7) (modify-all-frames-parameters '((font . "Lucida Sans Typewriter-9"))) (char-displayable-p ?\u25B7) --8<---cut here---end--->8--- Any idea why such differences? Best regards, Seb [1] http://www.scarfboy.com/coding/unicode-tool?s=U%2B25B7 I've had a chance to look at this now, and it doesn't seem to have anything to do with emacs. I've created a text file 25b7.txt (attached) with a single line containing the white right-pointing-triangle. When I issue the command "cat 25b7.txt" in a mintty terminal, I sometimes see an empty rectangle (meaning the character can't be displayed), and I sometimes see the white right-pointing triangle, depending on which font I select in the mintty options. I don't know enough about fonts and UTF-8 encoding to be able to shed any more light on this. Maybe someone else can help. Ken ▷ -- 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
Re: Unable to execute local scripts to run commands through SSH from Cygwin
Ken Brown cornell.edu> writes: > Does your script have DOS line endings? > > Ken > > Hi Ken: Bingo! Thanks for your help! Jim -- 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
Re: WARNING: Couldn't compute FAST_CWD pointer
On 2014-09-09 13:34, Eric Lu wrote: Got this warning message when using ssh on Windows command. I upgraded my notebook from Windows 8 to Windows 8.1, then it started having this message. Please make sure you have updated your Cygwin installation from a current mirror, and to be safe, reboot Windows. If that does not help, then we will need more information: Problem reports: http://cygwin.com/problems.html Yaakov -- 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
Re: Windows 2008 access to inetsrv directory
On 09/10/2014 10:59 AM, scotttins...@ups.com wrote: I have been puzzling over why a cygwin bash shell cannot access the c:\Windows\System32\inetsrv\backup directory. I have added "Users" and "cyg_server" account to directory permissions. I still cannot cd to or copy from the backup sub-directory. I saw postings regarding accessing certain System32 files failing with 32-bit apps. I tried creating a file system Junction link to the inetsrv directory, still no luck. Without knowing for sure, I'm going to guess that you're running on 64-bit Windows. If that's the case, what you're seeing is not Cygwin- specific. It's the Windows file system redirector that keeps 32-bit programs from accessing the ones in "System32" (oh the irony!) If you really want to do this, try looking down the c:\Windows\sysnative subtree instead. -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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
