Re: SIGINT default behavior

On Thu, Oct 8, 2009 at 12:19 AM, Pedro Izecksohn wrote: > Larry Hall wrote: >> I, Pedro Izecksohn, wrote: >>> >>>   The default behavior is not always the same. I also got: >>> ferror (stdin): >>>   and >>> ferror (stdin): Interrupted system call >>>   and the expected behavior of just the exit cod

ncurses: ncurses-config

Chuck, A few issues with ncurses-config: 1) The fact that there have been several (Cygwin-specific) ABI bumps to libncurses during the 5.x cycle (now at 9) doesn't change the fact that the API is still version 5, and other packages look for the script to be named ncurses5-config. 2) ncurses

Re: wise way to install cygwin packages

On Thu, Oct 8, 2009 at 12:49 AM, Larry Hall (Cygwin) wrote: > On 10/08/2009 12:25 AM, Ken Jackson wrote: >> >> On Wed, 7 Oct 2009 20:41:53 +0800 >> Steven Woody wrote: >>> >>> 3. So, after I do some other clicks to really deselect the PB, I have >>> to go back to deselect PA again! >> >> ... >>> >>

Re: wise way to install cygwin packages

On 10/08/2009 12:25 AM, Ken Jackson wrote: On Wed, 7 Oct 2009 20:41:53 +0800 Steven Woody wrote: 3. So, after I do some other clicks to really deselect the PB, I have to go back to deselect PA again! ... This make the operation very very hard to perform. I agree. And even for simple operati

Re: wise way to install cygwin packages

On Wed, 7 Oct 2009 20:41:53 +0800 Steven Woody wrote: > 3. So, after I do some other clicks to really deselect the PB, I have > to go back to deselect PA again! ... > This make the operation very very hard to perform. I agree. And even for simple operations I find it a bother to have to start up

Re: SIGINT default behavior

Larry Hall wrote: > I, Pedro Izecksohn, wrote: >> >>   The default behavior is not always the same. I also got: >> ferror (stdin): >>   and >> ferror (stdin): Interrupted system call >>   and the expected behavior of just the exit code 130. >> > > Try Cygwin 1.7 . $ c

Re: SIGINT default behavior

On 10/07/2009 11:10 PM, Pedro Izecksohn wrote: The default behavior is not always the same. I also got: ferror (stdin): and ferror (stdin): Interrupted system call and the expected behavior of just the exit code 130. Try Cygwin 1.7 . -- Larry Hall

SIGINT default behavior

r...@turion ~/programming/c/sigint $ cat test.c #include #include int main () { printf ("Press Control c\n"); char buffer [3]; char *fgets_returned = fgets (buffer, sizeof buffer, stdin); if (!fgets_returned) { if (ferror (stdin)) { perror ("ferror (stdin)"); return

fd leak in utimensat

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I haven't spent time trying to locate where the leak is happening, but process explorer confirms that this STC leaves a handle open to the file, preventing further re-creation of a new file by the same name. #include #include #include #include #in

-municode support

I think Cygwin should support -municode option. The following patches I made might be incorrect and/or incomplete. diff -u -N -r cygwin-1.7.0-62-old/winsup/mingw/conuni.c cygwin-1.7.0-62/winsup/mingw/conuni.c --- cygwin-1.7.0-62-old/winsup/mingw/conuni.c Thu Jan 1 00:00:00 1970 +++ cygwin-1.7.0

Re: gdb, insight, and tcltk

On Wed, Oct 07, 2009 at 05:46:56PM -0400, Charles Wilson wrote: >Chris -- > >Since gdb-7.0 was just released, I figure you'll probably be doing a >cygwin package fairly soon. However, I know you long to drop insight -- >at least to separate it out from gdb proper. > >So, I've got a proposal for you

gdb, insight, and tcltk

Chris -- Since gdb-7.0 was just released, I figure you'll probably be doing a cygwin package fairly soon. However, I know you long to drop insight -- at least to separate it out from gdb proper. So, I've got a proposal for you: I'll do an insight-only build (sans gdb.exe, gdb-tui.exe) which inst

Please, Help me!

Hello, (Excuse me for my bad English) I am from Brazil and I am asking for a small help. I could invent histories, but I think the truth works better! I am without work and I lost the hopes, this is last resource asking for donation through internet. I never thought that I would ask f

Rsync hanging

Hi. I just updated to 1.7 to see if it solved problems that I've been struggling with for a while with rsync hanging randomly on different files. I use rsync excessively, and on some systems it just works and never hangs-- but on some it hangs all the time. I'm transferring files via ssh; some

Re: BUG REPORT: Cygwin 1.7 installer

Dave Korn wrote: > Derek Kalweit wrote: >> If you add a \ to the end of the download path with the 1.7 installer, >> packages fail to download properly and the installer terminates with an >> error. I finally realized it was just an amateur mistake in the >> installer code and tried it without the

Re: BUG REPORT: Cygwin 1.7 installer

Derek Kalweit wrote: > If you add a \ to the end of the download path with the 1.7 installer, > packages fail to download properly and the installer terminates with an > error. I finally realized it was just an amateur mistake in the > installer code and tried it without the \, and it worked fine.

BUG REPORT: Cygwin 1.7 installer

If you add a \ to the end of the download path with the 1.7 installer, packages fail to download properly and the installer terminates with an error. I finally realized it was just an amateur mistake in the installer code and tried it without the \, and it worked fine. Adding a \ works in the produ

Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62

2009/10/7 Charles Wilson: > (On Vista, you can use SetConsoleScreenBufferEx -- which is supposedly > "documented" but I couldn't find any). There's a 'SetConsoleScreenBufferInfoEx'. But another one looks more interesting: 'SetCurrentConsoleFontEx' (also ≥Vista). Andy -- Problem reports: ht

does xinetd link against tcp wrapper

-- 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: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62

Thomas Wolff wrote: > It should be possible (and should be done then) to pre-configure at > least the Cygwin desktop link to use Lucida Console. It does not appear that the extended panels in the cmd.exe shortcut properties are available programmatically [*] The best I found was some utility code

Re: Additional carriage return added by cygwin commands to DOS text files

ttjqryfbndgdx wrote: Note that I don't have the issue with cat. bash-3.2$ cat test1 > test2 bash-3.2$ xxd test2 000: 6161 610d 0a62 6262 0d0a aaa..bbb.. "cat" consider input and output as binary. So the syntax "cat a > b" is always equivalent as "cp a b". Now if you think t

Re: Additional carriage return added by cygwin commands to DOS text files

Vincent Rivière freesbee.fr> writes: > > > I experienced the same issue with the "cat" command, and unfortunately I > > didn't find any transparent solution > > However a non-transparent hack is to use first a text filter then pipe > its output to the original command. The filter opens the f

Re: Additional carriage return added by cygwin commands to DOS text files

I experienced the same issue with the "cat" command, and unfortunately I didn't find any transparent solution :-( However a non-transparent hack is to use first a text filter then pipe its output to the original command. The filter opens the file in textmode so it gets rid of the CR. Then, as

Re: Additional carriage return added by cygwin commands to DOS text files

ttjqryfbndgdx wrote: I know it's a common issue, but I didn't find a solution to my problem in the archive. I have a "dos" file (lines ends with carriage return+line feed : 0d0a in Hex) : bash-3.2$ xxd test1 000: 6161 610d 0a62 6262 0d0a aaa..bbb.. If I apply a cygwin comman

Additional carriage return added by cygwin commands to DOS text files

I know it's a common issue, but I didn't find a solution to my problem in the archive. I have a "dos" file (lines ends with carriage return+line feed : 0d0a in Hex) : bash-3.2$ xxd test1 000: 6161 610d 0a62 6262 0d0a aaa..bbb.. If I apply a cygwin command to this file, I get a

Re: Cygwin setup.exe flagged by AVG as high level security threat because of Win32.AirCrack.c

On Wed, Oct 7, 2009 at 8:30 AM, Martin N Brampton wrote: > I cannot find any reference to AirCrack anywhere in documentation directly > related to Cygwin. Unless you got a bad copy of cygwin from a disreputable site, that someone has inserted a virus into, it doesn't contain aircrack or any other

wise way to install cygwin packages

Hi, I did not think this is a problem since in the past when I need to install cygwin, I always select all the packages in the installer (click the tree icon, make it switch from 'default' to 'install'). But now I plan not to install some packages when I do a fresh installation. So, I again, firs

Cygwin setup.exe flagged by AVG as high level security threat because of Win32.AirCrack.c

I cannot find any reference to AirCrack anywhere in documentation directly related to Cygwin. What information I can find through Google doesn't give me any idea why Cygwin would contain code for cracking passwords in wireless networks. It doesn't seem wise to install something that an anti-m

Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62

Corinna Vinschen wrote: On Oct 6 17:02, Andy Koppe wrote: 2009/10/6 Ken Brown: I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under

Re: Can't rm file, but no error message

Larry Hall (Cygwin cygwin.com> writes: > Get 'handle.exe' or 'procexp.exe' from sysinternals.com to > find out > who has handles still. Thanks a lot for pointing this out! Actually I had procexp installed, but was not aware that I can search for a file. I tried it out, and it seems to work wel

Re: Can't rm file, but no error message

Marc Girod gmail.com> writes: > /usr/lib/csih/getVolInfo Thank you, really useful! Filesystemname : Flags : 700ff FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMP

Re: R: Segfault with call to pthread_mutexattr_init under GDB

Marco Atzeri wrote: Da: Nicholas Sherlock This GDB was configured as "i686-pc-mingw32"... Have you tried the cygwin gbd ? $ gcc-4 -o prova prova.c $ gdb prova.exe GNU gdb 6.8.0.20080328-cvs (cygwin-special) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or

R: Segfault with call to pthread_mutexattr_init under GDB

> Da: Nicholas Sherlock > Oggetto: Segfault with call to pthread_mutexattr_init under GDB > A: cygwin cygwin.com > Data: Mercoledì 7 ottobre 2009, 08:53 > Hi everyone, > > I'm experiencing a crash while using GDB to debug a C > program that calls pthread_mutexattr_init. I recently > updated Cygw