Re: [xmlvm-dev] Several questions about generated code

[Shai <sha...@ya...>]

> I'm trying to look into this, it seems that the particular curThread is 

> broken the first time I reach this method. I'm trying to understand the 
> concept and why it fails for this particular case, as far as I understand 
> curThread ##uniqueId represents the unwindable stack of a particular stack frame 
> created within a try block. I just need to figure out how it got corrupted. 
> Maybe its a threading issue since I know the code I'm using has thread 
> related issues (which is why I occasionally get exceptions there).

I think the problem is in the generated code. I have a curThread_w23657aaac46b1c17 variable which is indeed invalid and the reason it is invalid is that the TRY that corresponds to that uniqueId wasn't executed before I reached this line.
So I'm guessing that this is a problem with the code generator, I'm trying to review my Java source code to see if there is something special there. The only thing that I can think of is that I have a large switch case in that code and most cases invoke return rather than breaking which is a less common practice. 
The switch is surrounded by a try/catch pair which might also be related in some way... 
I'll try making some code modifications to see if it works around the issue.