Re: [aspectj-dev] How thread-safe is (or should be) the weaver?

[Martin Lippert <lippert@xxxxxxx>]

Hi Andy,

> Yes, the weaver should be thread safe (although not re-entrant).  You
> can raise a bug, but you know I'll ask for a testcase :)  There was a
> recent issue with the typemap in the world having problems but that is
> now fixed - I presume you are on the latest code?

I am using the latest AJDT 1.5.2 build and raised this bug report:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=227029

Unfortunately I have no reproduceable testcase for this, but I have 
something else for you: I have found the cause of the problem, I think. 
I tried to describe it in the bug report. :-)

Cheers,
-Martin



> cheers,
>
> Andy.
>
> On 14/04/2008, Martin Lippert <lippert@xxxxxxx> wrote:
> > Hi!
> >
> >  I am currently tracking down a problem within Equinox Aspects and it seems
> > to be a multithreading problem within the weaver implementation.
> >
> >  My question is: Is the weaver meant to be thread-safe? If so, I would open
> > a bug report for this. If not, I would synchronize the access to the weaver
> > code from Equinox Aspects.
> >
> >  What do you think? What is the right way to go?
> >
> >  Thanks for your help!
> >
> >  -Martin
> >
> >
> >
> >  _______________________________________________
> >  aspectj-dev mailing list
> >  aspectj-dev@xxxxxxxxxxx
> >  https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev