Summary: | NullPointerException at AspectJElementHierarchy.java:677 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Jesse Englert <jenglert> | ||||
Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | aclement | ||||
Version: | unspecified | ||||||
Target Milestone: | 1.6.10 | ||||||
Hardware: | PC | ||||||
OS: | Windows Vista | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jesse Englert
2010-09-08 18:30:31 EDT
Created attachment 178463 [details]
JVM Error Log
I was able to reproduce this error when adding or removing the throws clause from the constructor...until Eclipse eventually crashed. Attaching the JVM hs_err log. The JVM identified the following:
# Problematic frame:
# J org.aspectj.asm.internal.AspectJElementHierarchy.updateHandleMap(Ljava/util/Set;)V
Possibly a threading issue with an AJDT thread affecting the handleMap which the compiler is in the middle of processing. A guard would seem to suffice here as null effectively means the same as the check the code was going to perform. Not sure why a simple NPE would lead to a vm crash. I've committed a guard on null to stop this occurring. |