This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libgcj/49455] New: Thread_Interrupt Looper subtest FAILs on IRIX


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]