JDK-6326210 : SAJDI: Null pointer exception while reading address of sender sp.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 5.0,6
  • Priority: P3
  • Status: Resolved
  • Resolution: Not an Issue
  • OS: linux,solaris
  • CPU: x86
  • Submitted: 2005-09-20
  • Updated: 2013-09-05
  • Resolved: 2013-06-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Duplicate :  
JDK-6357598 - SA: java.lang.NullPointerException from jstack on compiled frame
Description
Following test case fails  due to null pointer exception in
solaris x86 client vm  in -Xcomp mode.

 nsk/sajdi/StackFrame/getValues/getvalues001
 nsk/sajdi/StackFrame/thisObject/thisobj001
 nsk/sajdi/StackFrame/visibleVariables/visibvars001
 nsk/sajdi/VMCannotBeModifiedException/thrown/thrown003

The following test case some times fails for this same reason
on linux x86. The problem seems to be specific to x86 platform
not related to any specific OS.

nsk/sajdi/StackFrame/getValues/getvalues001
nsk/sajdi/StackFrame/thisObject/thisobj001
nsk/sajdi/StackFrame/visibleVariables/visibvars001
nsk/sajdi/ThreadReference/frame/frame002
nsk/sajdi/ThreadReference/frames/frames002
nsk/sajdi/ThreadReference/frames_ii/frames_ii002
nsk/sajdi/VMCannotBeModifiedException/thrown/thrown003


Here is stack trace for this failure:

#Find frame of tested method on the thread stack
#java.lang.NullPointerException
#	at sun.jvm.hotspot.runtime.Frame.addressOfStackSlot(Frame.java:204)
#	at sun.jvm.hotspot.runtime.x86.X86Frame.senderForCompiledFrame(X86Frame.java:269)
#	at sun.jvm.hotspot.runtime.x86.X86Frame.sender(X86Frame.java:212)
#	at sun.jvm.hotspot.runtime.Frame.sender(Frame.java:174)
#	at sun.jvm.hotspot.runtime.Frame.realSender(Frame.java:179)
#	at sun.jvm.hotspot.runtime.VFrame.sender(VFrame.java:102)
#	at sun.jvm.hotspot.runtime.CompiledVFrame.sender(CompiledVFrame.java:147)
#	at sun.jvm.hotspot.runtime.VFrame.javaSender(VFrame.java:129)
#	at sun.jvm.hotspot.jdi.ThreadReferenceImpl.privateFrames(ThreadReferenceImpl.java:202)
#	at sun.jvm.hotspot.jdi.ThreadReferenceImpl.frames(ThreadReferenceImpl.java:167)
#	at nsk.sajdi.VMCannotBeModifiedException.thrown.thrown003.runIt(thrown003.java:118)
#	at nsk.sajdi.VMCannotBeModifiedException.thrown.thrown003.run(thrown003.java:26)
#	at nsk.sajdi.VMCannotBeModifiedException.thrown.thrown003.main(thrown003.java:21)
Removed description from another bug.
This bug also affects the following NSK tests:

    nsk/sajdi/ThreadReference/frame/frame002
    nsk/sajdi/ThreadReference/frames/frames002
    nsk/sajdi/ThreadReference/frames_ii/frames_ii002
Comments
Let's close it and see if it turns up again.
24-06-2013
Is this bug still an issue? What is the latest Java version it's tested on? There were a few changes in the SA regarding verifying registers for stack walking... This bug was quoted as a possible reason 8000973 was not found earlier, and as being the cause of some testing exclusions?
20-06-2013
SUGGESTED FIX local webrev at http://jruntime.east.sun.com/~coleenp/webrev/6326210 Patchfile attached.
20-08-2010
EVALUATION This bug is same as bug 6357598.
11-07-2006
EVALUATION Looks like getFP() has returned null. Need to investigate this further to see why it is null. Looks like there is a bug in SA code in handling of FP. FP can be null in some cases.
20-09-2005