We're updating the issue view to help you get more done. 

Stack Trace output differs depending on compiler and architecture

Description

The stack trace output can differ depending on the architecture and compiler. This makes tests unreliable.

For example, for the regression test, the output for the IA32 compilers and the PPC baseline compiler is:

1 2 Exception in thread "MainThread" java.lang.NullPointerException at test.org.jikesrvm.basic.bugs.RVM_966.main(RVM_966.java:23)

For the PPC opt compiler on O1 it is:

1 2 3 4 5 6 Exception in thread "MainThread" java.lang.NullPointerException at java.lang.Exception.<init>(Exception.java:66) at java.lang.RuntimeException.<init>(RuntimeException.java:64) at java.lang.NullPointerException.<init>(NullPointerException.java:69) at org.jikesrvm.runtime.RuntimeEntrypoints.raiseNullPointerException(RuntimeEntrypoints.java:869) at test.org.jikesrvm.basic.bugs.RVM_966.main(RVM_966.java:23)

While writing the test for RVM-966, I ran into a similar problem on IA32: stack traces between baseline compier and opt compiler differed.

Environment

None

Status

Assignee

Erik Brangs

Reporter

Erik Brangs

Labels

None

External issue ID

None

Components

Fix versions

Affects versions

3.1.3

Priority

Low