From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: jingham@apple.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: patch to fix gdb/1680
Date: Mon, 21 Jun 2004 02:44:00 -0000 [thread overview]
Message-ID: <20040621024417.6A4F64B104@berman.michael-chastain.com> (raw)
> Note, this duplication of the regexp engine is what I wrote about a
> couple of weeks ago when removing expect first came up...
I found your message again after I posted mine ... now I feel dumb.
"Three months in the lab can often save thirty minutes in the library."
We're in pretty good shape with gdb because I've been using
stock TCL 8.4.6 + Expect 5.41 for a long time, years now.
So I've already swept the minefield, as it were.
> Finally, note that if you need to see the result regexp as it ACTUALLY
> gets to dejagnu, pass the --debug flag in RUNTESTFLAGS, and it will
> spit out a file named dbg.log in build/gdb/testsuite which shows among
> much other stuff the actual regexp that dejagnu is trying to match.
Wow, I didn't know about that. That will help me in the future.
Michael C
next reply other threads:[~2004-06-21 2:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 2:44 Michael Elizabeth Chastain [this message]
[not found] <1087626323.4926.ezmlm@sources.redhat.com>
2004-06-20 22:37 ` Jim Ingham
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 6:31 Michael Elizabeth Chastain
2004-06-21 5:00 ` Jim Blandy
2004-06-19 2:44 Michael Elizabeth Chastain
2004-06-19 6:25 ` Joel Brobecker
2004-06-18 23:38 Michael Elizabeth Chastain
2004-06-18 20:25 Michael Elizabeth Chastain
2004-06-18 20:33 ` Daniel Jacobowitz
2004-06-18 19:43 Michael Elizabeth Chastain
2004-06-18 19:18 Michael Elizabeth Chastain
2004-06-18 19:35 ` Andrew Cagney
2004-06-18 19:42 ` Daniel Jacobowitz
2004-06-18 19:56 ` Andrew Cagney
2004-06-18 20:00 ` Daniel Jacobowitz
2004-06-18 22:20 ` Jim Blandy
2004-06-18 22:51 ` Andreas Schwab
2004-06-19 6:15 ` Jim Blandy
2004-06-18 18:25 Michael Elizabeth Chastain
2004-06-18 18:10 Jim Blandy
2004-06-18 18:42 ` Daniel Jacobowitz
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=20040621024417.6A4F64B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.com \
/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