From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5169 invoked by alias); 17 Jun 2009 21:00:21 -0000 Received: (qmail 5157 invoked by uid 22791); 17 Jun 2009 21:00:20 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_33,J_CHICKENPOX_43,J_CHICKENPOX_53 X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.155) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 17 Jun 2009 21:00:13 +0000 Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.14.2/jtpda-5.5pre1) with ESMTP id n5HKwTEQ073187 ; Wed, 17 Jun 2009 22:58:29 +0200 (CEST) Received: from mailserver.u-strasbg.fr (ms2.u-strasbg.fr [IPv6:2001:660:2402:d::11]) by baal.u-strasbg.fr (8.14.0/jtpda-5.5pre1) with ESMTP id n5HKwTXa099302 ; Wed, 17 Jun 2009 22:58:29 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from d620muller (lec67-4-82-230-53-140.fbx.proxad.net [82.230.53.140]) (user=mullerp mech=LOGIN) by mailserver.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id n5HKwQEe056149 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Wed, 17 Jun 2009 22:58:28 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) From: "Pierre Muller" To: "'Eli Zaretskii'" , "'Daniel Jacobowitz'" Cc: , References: <001201c9ebb1$96414b10$c2c3e130$@u-strasbg.fr> <20090613150505.GA28157@caradoc.them.org> <000001c9ec65$9bf13ca0$d3d3b5e0$@u-strasbg.fr> <20090613235454.GA1893@caradoc.them.org> <20090614002516.GO25703@adacore.com> <000001c9ed8a$21cfdc30$656f9490$@u-strasbg.fr> <20090616145756.GB7730@adacore.com> <000c01c9eeda$022d8a70$06889f50$@u-strasbg.fr> <20090617133626.GA24310@caradoc.them.org> <000001c9ef88$959e9ac0$c0dbd040$@u-strasbg.fr> In-Reply-To: <000001c9ef88$959e9ac0$c0dbd040$@u-strasbg.fr> Subject: RE: [RFC] Improve testsuite for poor expect behavior Date: Wed, 17 Jun 2009 21:00:00 -0000 Message-ID: <001101c9ef8e$5e8b1ee0$1ba15ca0$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00452.txt.bz2 Whoops, I forgot that I also added djgpp target to the list of targets using set_unbuffered_mode in gdb.exp Otherwise tests like gdb.base/fileio.exp do fail all over the place. Pierre > -----Message d'origine----- > De=A0: gdb-patches-owner@sourceware.org [mailto:gdb-patches- > owner@sourceware.org] De la part de Pierre Muller > Envoy=E9=A0: Wednesday, June 17, 2009 10:17 PM > =C0=A0: 'Eli Zaretskii'; 'Daniel Jacobowitz' > Cc=A0: brobecker@adacore.com; gdb-patches@sourceware.org > Objet=A0: RE: [RFC] Improve testsuite for poor expect behavior >=20 > My way to use cygwin expect for DJGPP > is quite ugly, but it gives some results. >=20 > The basic idea is to consider that djgpp is a remote target and to > overload several expect procedures to cope with DJGPP specific > features. >=20 > I added a .dejagnu directory in my cygwin home, with an empty > site.exp file and a boards directory. > This directory stores several files, > but only one concerns DJGPP. > I simply called it djgpp.exp > and I run the testsuite > in > djbuild/gdb/testsuite > (with a DJGPP compiled gdb.exe at djgpp/gdb level). > I an sereral testsuite subsets using > make check RUNTESTFLAGS=3D"--target=3Ddjgpp --host_board=3Ddjgpp > gdb.*/wa*.exp" > Which means that the same file ($HOME/.dejagnu/boards/djgpp.exp) is > used both as host_board and target... > as I said it is really ugly, but I didn't have time to sort things out, > and I am not sure I will have the willingness to do it... >=20 > I attached the djpp.exp file. >=20 > The key functions are > djgpp_spawn and djgpp_exec > djgpp_exec uses a response file > for long commandlines, to overcome the > 80 chars limitations for Dos command lines. > In its present form, it prints out lots of information, send_user can > probably be changed to verbose if someone just wants to use it. >=20 > Eli, tell me if you get a chance to try it out. >=20 > Pierre >=20 >=20 > > -----Message d'origine----- > > De=A0: Eli Zaretskii [mailto:eliz@gnu.org] Envoy=E9=A0: Wednesday, June= 17, > > 2009 7:17 PM =C0=A0: 'Daniel Jacobowitz' > > Cc=A0: muller@ics.u-strasbg.fr; brobecker@adacore.com; gdb- > > patches@sourceware.org Objet=A0: Re: [RFC] Improve testsuite for poor > > expect behavior > > > > > Date: Wed, 17 Jun 2009 09:36:26 -0400 > > > From: 'Daniel Jacobowitz' > > > Cc: 'Joel Brobecker' , 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.