public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/18961] Large output causes testsuite failure
Date: Mon, 13 Dec 2004 17:56:00 -0000	[thread overview]
Message-ID: <20041213175619.10500.qmail@sourceware.org> (raw)
In-Reply-To: <20041213171434.18961.chris@bubblescope.net>


------- Additional Comments From chris at bubblescope dot net  2004-12-13 17:56 -------
I'm fairly sure it's not a timeout (It takes <5 seconds to run on my computer).
It might be a dejagnu bug. Unfortunatly I find it very hard to find out exactly
what is causing this bug.

While I agree that allowing program's output to run out of control is a bad
idea, the problem with the current cutoff system is that it seems quite
unreliable. Around the mark at which the bug occurs (round about 200,000-300,000
characters on my computer) the test will sometimes run and sometimes fail. This
kind of unpredictable behaviour led me to a merry afternoon of debugging (I was
writing a test which outputed a large quantity of state information for testing
reasons) as it randomly appeared and disappeared. I do think that the behaviour
could be more reliable, and at least better documented.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18961


  parent reply	other threads:[~2004-12-13 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 17:14 [Bug debug/18961] New: " chris at bubblescope dot net
2004-12-13 17:21 ` [Bug other/18961] " pinskia at gcc dot gnu dot org
2004-12-13 17:56 ` chris at bubblescope dot net [this message]
2005-02-07  4:51 ` jsm28 at gcc dot gnu dot org
2005-02-08 18:31 ` chris at bubblescope dot net

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=20041213175619.10500.qmail@sourceware.org \
    --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: 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).