Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro_alves@portugalmail.pt>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] gdb/testsuite/gdb.base/fileio.exp patch for cygwin
Date: Wed, 05 Dec 2007 09:22:00 -0000	[thread overview]
Message-ID: <001501c8371a$0a58faa0$1f0aefe0$@u-strasbg.fr> (raw)
In-Reply-To: <4755E78F.7000301@portugalmail.pt>

  I am sorry, Pedro,
but I am completely unable to reproduce
your output.
  I always get '1' as a result for all the tests
I tried running your application.
  I tried to compile the source as
gcc -g -o main.exe main.c
and in that case I got '1' for the three descriptors
in all case:
  1) run directly inside Cygwin bash
  2) run directly from cd.exe prompt (with a cygwin1.dll in the path)
  3) run inside current HEAD gdb
  4) run inside Cygwin special gdb distributed by Cygwin setup program
  5) run using gdb 6.3 for mingw32

If I add -mno-cygwin, I get '64' as a result instead of '1'
for all three descriptors, but then again
running the executable directly or within any of the gdb mentioned above
gives always '64'.



> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: Wednesday, December 05, 2007 12:50 AM
> To: Pierre Muller
> Cc: gdb-patches@sourceware.org
> Subject: Re: [RFC] gdb/testsuite/gdb.base/fileio.exp patch for cygwin
> 
> Pierre Muller wrote:
> > I tried to expose some cygwin testsuite problems related to the fact
> > that dejagnu does not seem to be able to fool the cygwin system, to
> > get it to believe that the output is not redirected.
> >
> > http://sourceware.org/ml/gdb/2007-11/msg00273.html
> >
> >   The main effect is that, Cygwin knowing that the output is
> > redirected to a non-tty, it will start to use file buffering that
> will
> > interact badly with the expectation of the gdb testsuite.
> >
> 
> I don't think that dejagnu is to blame here, and
> I believe the individual testfiles are the wrong place
> to fix this.  You can easily reproduce the symptoms
> in any run.  Try this with the attached patch:
> 
> #include <stdio.h>
> #include <stdlib.h>
> 
> int main ()
> {
>          printf ("isatty 0 = %d\n", isatty (0));
>          printf ("isatty 1 = %d\n", isatty (1));
>          printf ("isatty 2 = %d\n", isatty (2));
>          return 0;
> }

  How did you compile that source exactly?
> --------------------
> 
> Cygwin host:
> 
>  >./main.exe
> isatty 0 = 1
> isatty 1 = 1
> isatty 2 = 1
 Is this a cmd.exe prompt?

>  >gdb main.exe
> isatty (0) = 1
> isatty (1) = 1
> isatty (2) = 1
> ttyname (0) = /dev/tty2
> ttyname (1) = /dev/tty2
> ttyname (2) = /dev/tty2
  From where is this coming from?

> GNU gdb 6.7.50.20071201-cvs
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-cygwin"...
> (gdb) r
> Starting program: /home/pedro/isatty/main.exe
> isatty 0 = 0
> isatty 1 = 0
> isatty 2 = 0

   As said above, I never get this...

Pierre



  reply	other threads:[~2007-12-05  8:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 10:02 Pierre Muller
2007-12-04 23:50 ` Pedro Alves
2007-12-05  9:22   ` Pierre Muller [this message]
2007-12-05 22:56     ` Pedro Alves
2007-12-05 12:17   ` Corinna Vinschen
2007-12-05 19:19     ` Eli Zaretskii
2007-12-05 23:01     ` Pedro Alves
2007-12-06  1:06       ` Daniel Jacobowitz
2007-12-06  3:42         ` Pedro Alves
2007-12-06  4:25           ` Pedro Alves
2007-12-06 11:21             ` Corinna Vinschen
2007-12-07 13:54               ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001501c8371a$0a58faa0$1f0aefe0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox