public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/64983] Incomplete summary when regtesting with dejagnu 1.5.2. Date: Sat, 28 Mar 2015 18:07:00 -0000 [thread overview] Message-ID: <bug-64983-4-uMiJ5ppif2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64983-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983 --- Comment #6 from howarth at bromo dot med.uc.edu --- This same bug has also been reported on dejagnu mailing list at... http://lists.gnu.org/archive/html/dejagnu/2015-02/msg00000.html and claimed to be pinpointed to /usr/share/dejagnu/remote.exp... http://lists.gnu.org/archive/html/dejagnu/2015-03/msg00002.html Since there has been no changes to that file since 2013, I wonder if the buffer overflow is really just the manifestation of the bug and not the actual cause.
next prev parent reply other threads:[~2015-03-28 15:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-09 14:24 [Bug testsuite/64983] New: " dominiq at lps dot ens.fr 2015-02-09 14:36 ` [Bug testsuite/64983] " dominiq at lps dot ens.fr 2015-02-18 17:55 ` howarth at bromo dot med.uc.edu 2015-02-18 19:37 ` iains at gcc dot gnu.org 2015-02-18 20:15 ` howarth at bromo dot med.uc.edu 2015-02-18 20:21 ` iains at gcc dot gnu.org 2015-03-28 18:07 ` howarth at bromo dot med.uc.edu [this message] 2015-03-28 20:56 ` howarth at bromo dot med.uc.edu 2015-03-29 7:17 ` howarthjw at gmail dot com 2015-03-29 15:10 ` howarth.at.gcc at gmail dot com 2015-03-29 15:39 ` dominiq at lps dot ens.fr 2015-03-31 5:09 ` howarth.at.gcc at gmail dot com 2015-03-31 9:34 ` dominiq at lps dot ens.fr
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=bug-64983-4-uMiJ5ppif2@http.gcc.gnu.org/bugzilla/ \ --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).