Re: [aspectj-users] Variable evaluation in debugger not working with asp

["George Harley1" <GHARLEY@xxxxxxxxxx>]

Hi Oliver, 

We have been able to recreate some of the behaviour you describe in your notes.

In Eclipse 2.1.1 with AJDT 1.1.3 installed I can see that local variables in methods of plain ordinary Java classes don't always show in the "variables" view of the debug perspective when an aspect cuts across that class. The precise behaviour seems dependent on the type of local variable : for instance, an int never seems to show for me while a String only shows once it has been set to a non-null value. Other behaviours will be uncovered as the bug is analysed. A new bugzilla report has been opened on the apparent loss of debug information on local variables in a method. The number is 41536 which you can view here :  https://bugs.eclipse.org/bugs/show_bug.cgi?id=41536 .

So far, the "error evaluating" messages that you refer to have not shown up for me. I would be grateful if you could supply more information on how the simple test case can be enhanced to make these happen. We can either work together on this particular report to add more detailed information on these additional problems you are seeing or else open a new report altogether. 

Best regards,
George
________________________________________
George C. Harley

"Oliver Kuntze" <okuntze@xxxxxxx> Sent by: aspectj-users-admin@xxxxxxxxxxx 14/08/2003 09:04 Please respond to aspectj-users

To:        aspectj-users@xxxxxxxxxxx         cc:                 Subject:        [aspectj-users] Variable evaluation in debugger not working with aspectj project - Known but not public limitation of aspectj?

Hi all,

we are evaluating aspectj regarding its usability in future projects.

With eclipse 2.1.1 and ajdt 1.1.3 ist seems that one has only very limited
possibilities when it comes to debugging even regular java classes. For
example when trying to display variables while stepping through a method
the debugger in most of the cases reacts with a "Error evaluating" window
stating "foo cannot be resolved". I would say the probability of getting
this error while in a regular java class (no aspect) is about 0,8. So far I
have only read that  it is not possible to set breakpoints in aspects and
that debugging into aspects is not fully featured yet, but if the
possibilities of debugging my regular java classes would also be limited
when using an aspectj project that would really decrease development
productivity a lot.

Did I made some mistakes in configurating aspectj or is this a known but
not public limitation of the current aspectj version?

It would be great if someone could post a brief note and give me a hint.

Thanks a lot in advance!

Regards,

Oliver





_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users