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

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

Hi Paul,
I wouldn't necessarily define this as fortunate ;-)

Thanks for the tips, I normally keep the stack traces disabled by default.

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).

Thanks.

>

>Hi Shai,
>
>Fortunately you're not alone in experiencing the XMLVM_MEMCPY issue.  I am looking into this as well.  Let me know if you find anything.
>
>Aside from enabling NullPointerException and ArrayIndexOutOfBoundsException checks, you can also enable stack traces:
>
>#define XMLVM_ENABLE_STACK_TRACES
>
>All 3 of those are handy, but keep in mind they significantly decrease performance, especially checking for NullPointerExceptions.
>
>Thanks,
>Paul