Re: Re: Avoiding hitting the 64k limit on instrumentation

hmm not sure i quite understand you.
currently for each method node I pass it through an adapter which visits
each instruction, instrumenting it and passing the output to a class writer.

how does your approach fit in with this?


Prashant

Sent from my iPhone

On Apr 2, 2011, at 8:01 AM, Eugene Kuleshov <[email protected]> wrote:

You can put MethodNode to the end of the visitor chain and do your
verification in overwritten accept() method.

  regards,
  Eugene
 On 2011-04-02 10:56 AM, "Prashant Deva" <[email protected]> wrote:
> I want to somehow 'back out' of my instrumentation if I see that the
> instrumented method size is greater than the 64k limit.
> I know that you can use CodeSizeEvaluator to get the size after
> instrumenting the method.
>
> However I am curious if someone has suggestions for how to back out of the
> instrumentation and write the original bytes of the method if the 64k
limit
> is reached after instrumentation?
>
> Prashant


-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
<[email protected]><[email protected]>
For general help:
mailto:[email protected]?subject=help<[email protected]?subject=help><[email protected]?subject=help>
OW2 mailing lists service home page: http://www.ow2.org/wws

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws