From: Jim Ingham <jingham@apple.com>
To: gdb@sources.redhat.com
Subject: Re: [Gdb] removing src/dejagnu, src/expect
Date: Mon, 07 Jun 2004 21:37:00 -0000 [thread overview]
Message-ID: <F0BAB511-B8CA-11D8-A866-000A958F4C44@apple.com> (raw)
In-Reply-To: <1086598259.8126.ezmlm@sources.redhat.com>
Note, there are some local patches to Expect to switch the regular
expression engine that Expect uses from the new Unicode aware version
back to the original Henry Spencer one that shipped with Tcl 7.x. A
copy of the old Tcl regexp code was pulled into the src/ version of
Expect. This was done because the new regular expression engine was
subtly different from the old one, this might cause spurious testsuite
failures. The ChangeLog for this is:
2001-07-09 Ian Roxborough <irox@redhat.com>
* tclParse-compat.c: New file.
* tcl_regexp.c:
* tcl_regexp.h: New file. Contains Tcl8.0's regexp.
* Makefile.in: Added new files to be compiled and linked.
* exp_clib.c (exp_expectl, exp_fexpectl):
* exp_inter.c (in_keymap, Exp_InteractCmd ):
* exp_regexp.c (regtry, regdump, regprop):
* expect.c (parse_expect_args, eval_case_string,
exp_background_filehandler, Exp_ExpectCmd):
* expect.h:
* expect_comm.h:
* Dbg.c (breakpoint_test, cmdBreak): Use newly built in
regexp, not external Tcl regexp.
* exp_tty.c (exec_stty):
* exp_command.c (Exp_CloseCmd, Tcl_CloseCmd): Handle Tcl API
changes in Tcl8.3.
I just reran the gdb testsuite - on the Apple gdb but this shouldn't
make much difference - with the Expect 5.38 from the SourceForge
sources, and with Tcl 8.4.4, also from SourceForge, and I didn't see
any new failures compared with the expect & tcl from src/. But this
ought to be more broadly tested - and particularly with the gcc
testsuite, before you do this switch.
Needless to say, the Expect folks are not very likely to take Ian's
patch, since all it does is downgrades the regexp engine - sticking a
second copy in the Expect sources... So if there are new failures,
then somebody is going to have to go through and clean up the
testsuite.
Jim
On Jun 7, 2004, at 1:50 AM, gdb-digest-help@sources.redhat.com wrote:
>
>
> On Sat, Jun 05, 2004 at 10:39:42AM -0400, Michael Chastain wrote:
>>> At yesterday's GCC Summit testing BOF, there was a strong concensus
>>> that these directories should be removed from the src tree and that
>>> developers should install the latest releases of Expect and Dejagnu
>>> from their distribution/packaging system or from a source tarball at
>>> ftp.gnu.org.
>>
>> Err, I'm kinda surprised that the "GCC Summit" has enough src/
>> people to make decisions about src/. Are Andrew Cagney (gdb)
>> and Daniel Jacobowitz (binutils) there?
>
> Yes (although I skipped the testing BOF out of sleepiness :).
>
> I'm redirecting this to the main GDB list.
>
> --
> Daniel Jacobowitz
next parent reply other threads:[~2004-06-07 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1086598259.8126.ezmlm@sources.redhat.com>
2004-06-07 21:37 ` Jim Ingham [this message]
2004-06-09 2:24 Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 21:29 Michael Elizabeth Chastain
2004-06-09 0:54 ` Christopher Faylor
[not found] <1086697608.21986.ezmlm@sources.redhat.com>
2004-06-08 17:35 ` Jim Ingham
2004-06-07 21:58 Michael Elizabeth Chastain
2004-06-08 20:57 ` Christopher Faylor
[not found] <20040605143942.E37E74B104@berman.michael-chastain.com>
2004-06-05 16:13 ` 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=F0BAB511-B8CA-11D8-A866-000A958F4C44@apple.com \
--to=jingham@apple.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).