Opened 19 years ago

Closed 15 years ago

#1625 closed enhancement (wontfix)

Expect spawn patch is a workaround not a solution

Reported by: Matthew Burgess Owned by: lfs-book@…
Priority: lowest Milestone: Future
Component: Book Version: 6.2
Severity: trivial Keywords:

Description (last modified by Jeremy Huntwork)

According to the above bug report, our Expect patch that fixes spurious failures in the GCC testsuite isn't the correct approach. I would be grateful (as I'm sure TCL and Expect upstream would be) if someone could take the time to write a simple Expect script and/or a simple TCL script that tickles the same bug! Good luck :)

Attachments (1) (302 bytes ) - added by Matthew Burgess 18 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 by alexander@…, 19 years ago

Greg Schafer pointed me to this when I asked the same question:

comment:2 by Matthew Burgess, 19 years ago

Well, I've tried that test case. I've increased it to 150 lines and it still works as I'd expect (no pun intended!) it to. This is without patching expect at all, and compiling it up against tcl-8.4.11.

comment:3 by Jeremy Huntwork, 18 years ago

Description: modified (diff)
Milestone: Future

comment:4 by archaic@…, 18 years ago

What is the status of this bug? Has anyone done more testing?

comment:5 by archaic@…, 18 years ago

Priority: normallowest
Severity: normaltrivial
Type: defectenhancement
Version: SVNunspecified

Dropping priority and moving to unspecified milestone. I'd like to close it as WONTFIX, but Matt may have other ideas.

comment:6 by Matthew Burgess, 18 years ago

I'd prefer if we keep it open. It'll take a more committed person than me to try and get the TCL and Expect devs to cooperate and recognize there is a problem. Last time I tried, folks couldn't even reproduce the problem (IIRC one person tried, but they were running the test case on an already patched version of Expect that was in Ubuntu!).

comment:7 by bdubbs@…, 18 years ago

Milestone: Future6.3
Version: unspecified6.2

by Matthew Burgess, 18 years ago

Attachment: added

comment:8 by Matthew Burgess, 17 years ago

Milestone: 6.3Future

We're not going to get this addressed by 6.3. Shifting to 'future'.

comment:9 by gerard@…, 15 years ago

Resolution: wontfix
Status: newclosed

Closing this for now. Not very hopeful in seeing it resolved any time soon. Reopen at a later date if somebody decides to tackle this one. Seems majority is content to leave it status quo.

Note: See TracTickets for help on using tickets.