public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chewi at aura-online dot co dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/37051] New: Random failures running ECJ 3.4 (threading problem?) Date: Thu, 07 Aug 2008 23:32:00 -0000 [thread overview] Message-ID: <bug-37051-16571@http.gcc.gnu.org/bugzilla/> (raw) I have been encountering random failures when running ECJ 3.4. ECJ 3.3 works fine and I did also encounter random failures with Sun's VM so I initially filed a bug at eclipse.org. However, further tests have indicated that there are two different issues here, one affecting GCJ and one affecting Sun, hence I am filing this bug report now. The failures only occur when ECJ is run with multiple threads. They do not occur when -Djdt.compiler.useSingleThread=true is specified and they also do not occur on single core machines. I have only seen the failures on the x86_64 platform but it could possibly affect others too. The frequency of the failures varies but they usually occur around once every 10 tries. The error messages also vary but they usually look like this. java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:160) at java.lang.Thread.run(libgcj.so.90) java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.util.Util.getFileCharContent(Util.java:226) at org.eclipse.jdt.internal.compiler.batch.CompilationUnit.getContents(CompilationUnit.java:71) at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:160) at java.lang.Thread.run(libgcj.so.90) I have reproduced this on my usual Gentoo Linux system but also managed to reproduce it on a fresh installation of Ubuntu Intrepid Ibex Alpha 3 under KVM. So far, I have only tried GCC 4.3.1. For more details, see the original bug report at... https://bugs.eclipse.org/bugs/show_bug.cgi?id=241225 -- Summary: Random failures running ECJ 3.4 (threading problem?) Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: chewi at aura-online dot co dot uk GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37051
next reply other threads:[~2008-08-07 23:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-07 23:32 chewi at aura-online dot co dot uk [this message] 2008-08-10 20:23 ` [Bug java/37051] " pinskia at gcc dot gnu dot org 2008-08-10 20:59 ` chewi at aura-online dot co dot uk 2008-10-24 13:43 ` aph at gcc dot gnu dot org 2008-10-24 14:01 ` chewi at aura-online dot co dot uk 2008-12-27 14:50 ` pinskia at gcc dot gnu dot 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-37051-16571@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).