Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 'Daniel Jacobowitz' <drow@false.org>
Cc: muller@ics.u-strasbg.fr, brobecker@adacore.com,
		gdb-patches@sourceware.org
Subject: Re: [RFC] Improve testsuite for poor expect behavior
Date: Wed, 17 Jun 2009 17:17:00 -0000	[thread overview]
Message-ID: <E1MGykn-0008Q2-L1@fencepost.gnu.org> (raw)
In-Reply-To: <20090617133626.GA24310@caradoc.them.org> (message from 'Daniel 	Jacobowitz' on Wed, 17 Jun 2009 09:36:26 -0400)

> Date: Wed, 17 Jun 2009 09:36:26 -0400
> From: 'Daniel Jacobowitz' <drow@false.org>
> Cc: 'Joel Brobecker' <brobecker@adacore.com>, gdb-patches@sourceware.org
> 
> I have not tried this on DJGPP at all.

You cannot try this with DJGPP, because there are no such APIs in
DJGPP (with the exception of `setmode', which does exist).  Also,
there are no pipes in DJGPP.

I cannot judge what would be needed for DJGPP, since Pierre did not
yet explain how does he run DJGPP with the test suite, nor show any
code that achieves that.  All I can say is that DJGPP has the
`setmode' function that can be used to switch a standard handle into
binary mode, and that `isatty' is available to detect whether a handle
is connected to a terminal device.  Note that the DJGPP build of GDB
generally does not always use file I/O functions to write to the
terminal; it uses direct screen I/O for some ops.  Thus, binary mode
file I/O not necessarily will solve the problem that bothers Pierre,
although I do not yet understand fully whether it is relevant to DJGPP
as it is to MinGW.


  parent reply	other threads:[~2009-06-17 17:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 23:00 Pierre Muller
2009-06-13 14:52 ` Doug Evans
2009-06-13 15:05 ` Daniel Jacobowitz
2009-06-13 20:29   ` Pierre Muller
2009-06-13 23:55     ` 'Daniel Jacobowitz'
2009-06-14  0:25       ` Joel Brobecker
2009-06-15  7:23         ` Pierre Muller
2009-06-16 14:58           ` Joel Brobecker
2009-06-16 23:29             ` Pierre Muller
2009-06-17 13:36               ` 'Daniel Jacobowitz'
2009-06-17 14:54                 ` Joel Brobecker
2009-06-17 17:25                   ` Eli Zaretskii
2009-06-17 19:39                     ` Joel Brobecker
2009-06-18 14:38                       ` Eli Zaretskii
2009-06-18 14:59                         ` Joel Brobecker
2009-06-18 15:25                           ` Eli Zaretskii
2009-06-18 15:33                             ` Joel Brobecker
2009-06-18 15:58                               ` Samuel Bronson
2009-06-18 23:02                               ` Eli Zaretskii
2009-06-17 17:17                 ` Eli Zaretskii [this message]
2009-06-17 20:17                   ` Pierre Muller
2009-06-17 21:00                     ` Pierre Muller
2009-06-18 14:33                     ` Eli Zaretskii
2009-06-18 15:57                       ` Pierre Muller
2009-06-18 16:08                         ` Pedro Alves
2009-06-18 23:18                           ` Eli Zaretskii
2009-06-18 16:19                         ` Pedro Alves
2009-06-17 21:56                   ` Pierre Muller
2009-06-18 14:48                     ` Eli Zaretskii
2009-06-17 22:39                 ` Pierre Muller
2009-06-17 22:43                   ` 'Daniel Jacobowitz'
2009-06-17 22:54                     ` Pierre Muller
2009-06-17 23:21                       ` 'Daniel Jacobowitz'
2009-06-17 23:18                     ` Joel Brobecker
2009-06-18  6:31                       ` Mark Kettenis
2009-06-23 18:14               ` Joel Brobecker

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=E1MGykn-0008Q2-L1@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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