From: Doug Evans <dje@google.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Improve testsuite for poor expect behavior
Date: Sat, 13 Jun 2009 14:52:00 -0000 [thread overview]
Message-ID: <e394668d0906130752o65c957c3qa53dd9ce68c8138b@mail.gmail.com> (raw)
In-Reply-To: <001201c9ebb1$96414b10$c2c3e130$@u-strasbg.fr>
On Fri, Jun 12, 2009 at 5:00 PM, Pierre Muller<muller@ics.u-strasbg.fr> wrote:
> I am trying to run the testsuite in a cygwin environment,
> but for mingw32 or djgpp targets, using native builds of GDB.
>
> [...]
>
> 2009-06-12 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * lib/gdb.exp (fuzzy_newline): New global.
> (input_not_from_terminal): New global.
> (gdb_input_not_from_terminal): New procedure.
> (gdb_proc_unload): Add pattern corresponding to automated answer
> if not from terminal.
> (delete_breakpoints): Likewise.
> (gdb_run_mcd): Likewise.
> (gdb_start_cmd): Likewise.
> (gdb_internal_error_resync): Likewise.
> (gdb_reinitialize_dir): Likewise.
> (default_gdb_exit): Likewise.
> (gdb_file_cmd): Likewise.
> (rerun_to_main): Likewise.
> (gdb_compile): Also compile set_unbuffered_output
> for djgpp target.
> (gdb_expect): If fuzzy_newline is set, replace all "\r\n"
> by "\r+\n" in expcode.
Hi. I went through the patch.
It's fine with me, fwiw of course.
[I didn't spend _too_ much time vetting the regsub's, but in principle
it seems fine.]
next prev parent reply other threads:[~2009-06-13 14:52 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 [this message]
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
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=e394668d0906130752o65c957c3qa53dd9ce68c8138b@mail.gmail.com \
--to=dje@google.com \
--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