public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/12096] dejagnu truncates output from spawned commands randomly, causing intermittant failed tests Date: Tue, 27 Jan 2004 17:09:00 -0000 [thread overview] Message-ID: <20040127170948.14458.qmail@sources.redhat.com> (raw) In-Reply-To: <20030828173345.12096.dank@kegel.com> ------- Additional Comments From dank at kegel dot com 2004-01-27 17:09 ------- The patch seems to do the trick. It's required even if you're using the latest expect. I hope it gets integrated into the expect mainline. Not sure what the next step is here, but I'll mark this as FIXED to indicate that anyone who runs into this can get around it by building an expect with the patch. I'll also include this in the crosstool patch repository at http://kegel.com/crosstool -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12096
next prev parent reply other threads:[~2004-01-27 17:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-28 17:33 [Bug other/12096] New: " dank at kegel dot com 2003-11-02 22:37 ` [Bug other/12096] " pinskia at gcc dot gnu dot org 2003-11-02 22:51 ` jsm at polyomino dot org dot uk 2003-11-03 0:36 ` dank at kegel dot com 2003-11-03 1:51 ` pinskia at gcc dot gnu dot org 2003-11-03 2:35 ` pinskia at gcc dot gnu dot org 2003-11-05 0:39 ` dhazeghi at yahoo dot com 2004-01-17 23:57 ` dhazeghi at yahoo dot com 2004-01-24 6:08 ` markkp at msm dot umr dot edu 2004-01-27 17:09 ` dank at kegel dot com [this message] 2004-01-27 17:19 ` jsm at polyomino dot org dot uk 2004-01-27 17:36 ` dhazeghi at yahoo dot com 2004-01-28 16:47 ` pinskia at gcc dot gnu dot org 2005-02-08 18:49 ` chris at bubblescope dot net 2005-06-10 15:35 ` themis_hv at yahoo dot co dot uk
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=20040127170948.14458.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).