Databases
StackOverflow2013
Postsdbo
POJVM segmentation faults due to "Invalid memory access of location"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJVM segmentation faults due to "Invalid memory access of location"
    primarykey
    data
    text
    <p>I have a small project written in Scala 2.9.2 with unit tests written using ScalaTest. I use SBT for compiling and running my tests.</p> <p>Running <code>sbt test</code> on my project makes the JVM segfault regularly, but just compiling and running my project from SBT works fine. Here is the exact error message:</p> <pre><code>Invalid memory access of location 0x8 rip=0x10959f3c9 [1] 11925 segmentation fault sbt </code></pre> <p>I cannot locate a core dump anywhere, but would be happy to provide it if it can be obtained.</p> <p>Running <code>java -version</code> results in this:</p> <pre><code>java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-11M3909) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode) </code></pre> <p>But I've also got Java 7 installed (though I was never able to actually run a Java program with it, afaik).</p> <p>Another issue that may be related: some of my test cases contain titles including parentheses like <code>(</code> and <code>)</code>. SBT or ScalaTest (not sure) will consequently insert square parens in the middle of the output. For example, a test case with the name <code>(..)..(..)</code> might suddenly look like <code>(..[)..](..)</code>.</p> <p>Any help resolving these issues is much appreciated :-)</p> <p><strong>EDIT:</strong> I installed the Java 7 JDK, so now <code>java -version</code> shows the right thing:</p> <pre><code>java version "1.7.0_07" Java(TM) SE Runtime Environment (build 1.7.0_07-b10) Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) </code></pre> <p>This also means that I now get a more detailed segfault error and a core dump:</p> <pre><code># # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000000010a71a3e3, pid=16830, tid=19459 # # JRE version: 7.0_07-b10 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.3-b01 mixed mode bsd-amd64 compressed oops) # Problematic frame: # V [libjvm.dylib+0x3cd3e3] </code></pre> <p>And <a href="https://gist.github.com/4240715" rel="nofollow">the dump</a>.</p> <p><strong>EDIT</strong>: Changing the scalaVersion to 2.9.1 gave the following error once, then the same error as above:</p> <pre><code>Could not load hsdis-amd64.dylib; library not loadable; PrintAssembly is disabled [thread 25091 also had an error] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDan
    1. USDan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJVM segmentation faults due to "Invalid memory access of location"
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJVM segmentation faults due to "Invalid memory access of location"
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJVM segmentation faults due to "Invalid memory access of location"
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you get a minimal set of code and unit tests that still reproduces the problem, and post that?
      singulars
      1. POJVM segmentation faults due to "Invalid memory access of location"
      1. USThe Archetypal Paul
    2. COI'll try. I have busy weekend, so I'll get back to you next week.
      singulars
      1. POJVM segmentation faults due to "Invalid memory access of location"
      1. USDan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload