[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] AspectJ LTW and Cobertura

Hi Scott,

I've seen problems previously with weaving cobertura instrumented
code, but they were rather more fatal errors than what you are seeing.
 I'm not aware of others using annotation style aspects with
cobertura, the other users were using code style aspects I think.

If you are able to get a problematic class and the aspect class to me,
I will take a look - either via a bug report or email.  if it is too
sensitive to send through, we'll have to work something else out...
did your decompilation include looking at all private methods too?

We had a bug a while back about annotation style incorrectly looking
for debug info attached to abstract methods but that was fixed in
1.5.4.

Andy.

2009/6/4 Scott Frederick <scottyfred@xxxxxxxxx>:
> We are using AspectJ LTW and Cobertura for code coverage. Class files are
> weaved just fine if they are not instrumented with Cobertura, but when
> AspectJ attempts to weave the same aspects into Cobertura-instrumented
> copies of the same class files, weaving fails with the following error:
>
>
>
>>> error at com\mycompany\MyAspect.java::0 Cannot read debug info for
>>> @Aspect to handle formal binding in pointcuts (please compile with 'javac
>>> -g' or '<javac debug='true'.../>' in Ant)
>
>
>
> Decompiling the instrumented class file indicates that the debug info is in
> fact present in the uninstrumented and instrumented class file.
>
>
>
> We are using Cobertura 1.9 and AspectJ 1.6.4. Anyone know what’s going on
> here?
>
>
>
> Scott
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>