public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/49455] New: Thread_Interrupt Looper subtest FAILs on IRIX
Date: Fri, 17 Jun 2011 14:00:00 -0000	[thread overview]
Message-ID: <bug-49455-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: Thread_Interrupt Looper subtest FAILs on IRIX
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: tromey@gcc.gnu.org, aph@gcc.gnu.org
              Host: mips-sgi-irix6.5
            Target: mips-sgi-irix6.5
             Build: mips-sgi-irix6.5


The Looper subtest of Thread_Interrupt FAILs on IRIX 6.5, as can be seen in
the following diff between expected and found outputs:

---
/vol/gcc/src/hg/trunk/local/libjava/testsuite/libjava.lang/Thread_Interrupt.out
    Mon Mar  1 20:33:06 2010
+++ Thread_Interrupt.out        Fri Jun 10 17:14:23 2011
@@ -3,6 +3,6 @@
 sleep()
 interrupted - ok
 Busy waiting
-interrupted - ok
+Error: Busy wait was not interrupted.
 join()
 interrupted - ok

Unfortunately, if running the test under gdb, it just hangs in the first
subtest,
so the only hope was adding debug printfs.  Strangely, when I added
fprintf (stderr, "<Fn>: <args>\n") calls to all functions in posix-threads.cc,
the test suddenly passes when ignoring the debug output.

I'm somewhat at at loss how to further debug this.


             reply	other threads:[~2011-06-17 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 14:00 ro at gcc dot gnu.org [this message]
2011-07-19 15:02 ` [Bug libgcj/49455] " ro at gcc dot gnu.org
2014-06-13 11:43 ` ro at gcc dot gnu.org

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-49455-8172@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).