Bug 310144 - java.lang.RuntimeException at AsmManager.java:1143
Summary: java.lang.RuntimeException at AsmManager.java:1143
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 1.6.9M2   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-22 12:18 EDT by Cyprien NOEL CLA
Modified: 2010-05-13 13:48 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cyprien NOEL CLA 2010-04-22 12:18:39 EDT 
Build Identifier: Eclipse AspectJ Development Tools  Version: 2.0.3.e35x-20100419-1200 AspectJ version: 1.6.9.20100416110000

java.lang.RuntimeException
at org.aspectj.asm.AsmManager.removeSingleNode(AsmManager.java:1143)
at org.aspectj.asm.AsmManager.removeRelationshipsTargettingThisType(AsmManager.java:798)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1173)
at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter.weaveQueuedEntries(AjPipeliningCompilerAdapter.java:455)
at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter. ...  for handle =xstm/stm<com.argilsoft.xstm.core{TKeyed.java[TKeyed[Visitor?field-set(java.util.ArrayList com.argilsoft.xstm.core.Visitor._continueStack)

Reproducible: Sometimes

Steps to Reproduce:
Random exception popup in Eclipse
Comment 1 Andrew Clement CLA 2010-04-22 14:46:49 EDT 
it is a problem with attempting to remove a node from the structuremodel on an incremental build.  wonder why it can't be found... hmmm
Comment 2 Andrew Clement CLA 2010-04-29 15:55:16 EDT 
as being unable to delete something isn't the end of the world (it must already have been removed), I'm demoting this from an exception to a message (the message will just go to the console).  This means compilation won't be interrupted.  If there turn out to be downstream issues due to deletion failing, we can revisit this problem.