Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, "'Daniel Jacobowitz'" <drow@false.org>
Subject: RE: [RFC] Improve testsuite for poor expect behavior
Date: Tue, 16 Jun 2009 23:29:00 -0000	[thread overview]
Message-ID: <000c01c9eeda$022d8a70$06889f50$@u-strasbg.fr> (raw)
In-Reply-To: <20090616145756.GB7730@adacore.com>

Thanks, this is indeed very helpful
for mingw32 or djgpp target.
I simply added a line

set GDBFLAGS { -ex "set interactive on"}

at the end of site.exp in gdb/testsuite directory

  Nevertheless, it only addresses part of
the purpose of my patch.
  The problem of the extra '\r' generated by 
text mode output is still not solved.
  I will try to resubmit a much shorter patch
that just handles this without trying to
modify the executables.

Pierre

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Tuesday, June 16, 2009 4:58 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org; 'Daniel Jacobowitz'
> Objet : Re: [RFC] Improve testsuite for poor expect behavior
> 
> > > Yeah - we use that in two situations, one of them being our
> testsuite.
> > > I can resend if it helps.
> >
> > Yes, please.  This would be very helpful to check if my solution
> > brings something more or if yours should be used.
> 
> Here it is. I've extracted it from our tree, and the patch itself is
> pretty raw - needs testing and documentation, but it should allow you
> to see whether that helps or not in your case. I'll finish up the patch
> as soon as you confirm it's helping.
> 
> --
> Joel


  reply	other threads:[~2009-06-16 23:29 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 [this message]
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
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='000c01c9eeda$022d8a70$06889f50$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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