Bug 298067 - Compile error: RuntimeException thrown: Assertion is false
Summary: Compile error: RuntimeException thrown: Assertion is false
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-17 07:21 EST by franklinfk CLA
Modified: 2011-04-28 14:19 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description franklinfk CLA 2009-12-17 07:21:53 EST
Build Identifier: 20090920-1017

java.lang.RuntimeException
at org.aspectj.asm.AsmManager.verifyAssumption(AsmManager.java:1170)
at org.aspectj.asm.AsmManager.removeSingleNode(AsmManager.java:1102)
at org.aspectj.asm.AsmManager.removeRelationshipsTargettingThisType(AsmManager.java:779)
at org.aspectj.weaver.bcel.BcelWeaver.weave(BcelWeaver.java:1169)
at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter.weaveQueuedEntries(AjPipeliningCompilerAdapter.java:43 ... run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Compile error: RuntimeException thrown: Assertion is false

Reproducible: Always
Comment 1 Andrew Clement CLA 2009-12-30 13:03:29 EST
looks like an issue with model repair during an incremental build.  I don't suppose you have a small sample of code that triggers this?
Comment 2 Andrew Clement CLA 2010-01-11 14:29:09 EST
I am changing the diagnostics so that when this happen it will tell us which node could not be deleted from the model.  At least if we know that we may be able to create a small testcase that indicates the problem.
Comment 3 Andrew Clement CLA 2011-04-28 14:19:07 EDT
diagnostics are in place, don't seem to have triggered recently, reducing priority.