git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [JGIT] Bus error (SIGBUS) on Solaris

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
May 24, 2009, 20:11 UTC
Message-ID
<200905242211.19708.robin.rosenberg.lists@dewire.com>
In-Reply-To
<3ae83b000905241113u6895a7edlc1f81f0ea54a0c53@mail.gmail.com>
söndag 24 maj 2009 20:13:24 skrev John Bito:
Show 14 quoted lines
> I updated with the integration build on the update site today, after
> restart, Eclipse failed with a bus error.
> 
> > #  SIGBUS (0xa) at pc=0xf88162fc, pid=15191, tid=23
> > #
> > # Java VM: Java HotSpot(TM) Client VM (11.2-b01 mixed mode solaris-sparc)
> > # Problematic frame:
> > # j  org.spearce.jgit.lib.OffsetCache.getOrLoad(Lorg/spearce/jgit/lib/PackFile;J)Ljava/lang/Object;+17
> 
> I haven't updated my WinVista workstation, yet.  Shall I create a bug
> report with the full error log, or is this something that's already
> known?
> 
> The failure seems repeatable with my current workspace configuration.

There is no way a Java bug can crash the VM by itself. You can hit either a real VM bug or a bug in native code used by the VM.

So you have one or more
1) A broken Windows installation (some might consider this an tautology).
2) A corrupt JRE installation. Reinstall and see if things works better
3) A corrupt Eclipse. Try a fresh Eclipse.
4) Bad hardward, memory, malware leading to broken files (1).

2 & 3 are easy to test. If reinstalling the JRE doesn't help, try t he newest JRE available from SUN and see, Sun JVM bug reports should go to SUN. We will do absolutely nothing with them, though it would be interesting to get the ticket id when it gets assigned one.

-- robin '

Previous: John Bito
Message 2 of 2 in “[JGIT] Bus error (SIGBUS) on Solaris”
  1. John BitoMay 24, 2009
  2. Robin RosenbergMay 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.