[ews.eclipse.technology.aspectj] Re: Can AspectJ identify synthetic fiel

["Lefty A. Rivera" <lefty@xxxxxxxxxx>]

Adrian Colyer wrote:
> Lefty A. Rivera wrote:
>
> > I have a class and when I compiled it, I see synthetic fields when 
> > using a decompiler. If I try to weave the class and run the resulting 
> > woven class in JUnit the VM crash always. If there a way to avoid this?
>
>
> That sounds like something serious is going wrong somewhere! What VM are 
> you using? Is at an IBM 1.4.x perhaps?? And what level of the AspectJ 
> compiler did you use? The AspectJ weaver understands synthetic fields 
> quite happily - so the fact that your compiled class has them /may/ not 
> be relevant to the problem.
>
> Could you raise a bugzilla report please with details of:
>
> * The VM you are using
> * The AspectJ compiler version (or AJDT version / build date if this is 
> via AJDT)
> * The class being woven
> * The aspect(s) you are weaving into it
> * The .class file of the offending class both before weaving and after 
> weaving added as attachments would be very helpful too
>
> Thanks!
> -- Adrian.
I'm using a:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20050609 
JIT enabled: jitc)).

Let me add the synthetic fields were added by EMMA instrumentation, does 
this make any difference?.

How can I tell AspectJ to ignore a line like this  :
boolean aflag[] = ($VRc != null ? $VRc : $VRi())[0];


If not I'll open a Bugzilla bug. :-(.