Re: SIGINT default behavior

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 09:43:32AM -0400, Christopher Faylor wrote: >On Thu, Oct 08, 2009 at 05:53:47AM -0300, Pedro Izecksohn wrote: >>I, Pedro Izecksohn wrote: >>> Robert Pendell wrote: I was unable to reproduce this bug on 1.7. ??Compiled using GCC 4.3.4 on 1.7.0-62. ??Gave exit

Re: SIGINT default behavior

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 05:53:47AM -0300, Pedro Izecksohn wrote: >I, Pedro Izecksohn wrote: >> Robert Pendell wrote: >>> >>> I was unable to reproduce this bug on 1.7. ??Compiled using GCC 4.3.4 >>> on 1.7.0-62. ??Gave exit code 130 every time. ??I used your test case to >>> do the test. >> >> ??

Re: SIGINT default behavior

2009-10-08 Thread Corinna Vinschen
On Oct 8 05:53, Pedro Izecksohn wrote: > I, Pedro Izecksohn wrote: > > Robert Pendell wrote: > >> > >> I was unable to reproduce this bug on 1.7.  Compiled using GCC 4.3.4 > >> on 1.7.0-62.  Gave exit code 130 every time.  I used your test case to > >> do the test. > > > >  May be I did not expr

Re: SIGINT default behavior

2009-10-08 Thread Pedro Izecksohn
I, Pedro Izecksohn wrote: > Robert Pendell wrote: >> >> I was unable to reproduce this bug on 1.7.  Compiled using GCC 4.3.4 >> on 1.7.0-62.  Gave exit code 130 every time.  I used your test case to >> do the test. > >  May be I did not express myself well: > >  When ctrl c is pressed, it always

Re: SIGINT default behavior

2009-10-08 Thread Pedro Izecksohn
Robert Pendell wrote: > > I was unable to reproduce this bug on 1.7.  Compiled using GCC 4.3.4 > on 1.7.0-62.  Gave exit code 130 every time.  I used your test case to > do the test. May be I did not express myself well: When ctrl c is pressed, it always give exit code 130. The inconsistenci

Re: SIGINT default behavior

2009-10-07 Thread Robert Pendell
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

Re: SIGINT default behavior

2009-10-07 Thread Pedro Izecksohn
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

2009-10-07 Thread Larry Hall (Cygwin)
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

2009-10-07 Thread Pedro Izecksohn
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