I will try your suggestions. In the meantime, can you point me to how I would go about converting this problem to a test case? I'm not even sure if I can reproduce it yet. I haven't been able to identify what specifically caused the problem. My original coroutine prototype was using a <String, Continuation> map where the "yield statement" (a method call) would just yield to a continuation identified by a string name. I copied that logic verbatim, basically just changing the types. Of course, there's a lot more going on in the interpreter, so it's probably something to do with that.
On Mon, Jun 27, 2011 at 3:03 AM, Torsten Curdt <[email protected]> wrote: > Hey Jeff, > > the good news - I was able to reproduce it with your code base. > Both the exceptions during rewrite and the exception during resume. > > I haven't looked at the ASM code in a long time. Seems like there is > something fishy going on. Maybe the exceptions prevent proper > instrumentation. I would have to dig into that. > > There a couple of things you can try. > > - Try the ClassLoader based rewriting to see if you still get the > exceptions > - Question is why the classes cannot be found. Check the classpath. > - Give the old BCEL rewriting a try. Just to compare the results. > > Either way - a test case that can reproduce this in the javaflow tests > would make it much easier for me to help you out. > > HTH > > cheers, > Torsten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
