Re: Re: Re: Re: Re: Fwd: Re: More precise values in Analyzer
Eugene Kuleshov <[email protected]>
| Newsgroups | gmane.comp.java.objectweb.asm |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Jul 16, 2010 at 9:50 AM, Joshua Warner <[email protected]> wrote: > That is all fine, but it still leaves the problem of how to detect what > local variable slot that value was created from, without modifying the > Analyzer. Sorry, but I don't understand your issue. Let's break it into pieces: * at the beginning of the method you have initial values for this and method parameters in a well defined variable slots, which you can tell based on the method descriptor (for those values SourceValue would have an empty set) * somewhere in a middle of method you got a value in a certain variable slot this value can only came only from xSTORE opcode * somewhere in a middle of method you got a value on one of the stack slots. this value can came from one of the following: ** xLOAD opcode - here you know the variable from the opcode instruction ** value returned from the method call (type is normally is in the method descriptor) ** value created from some other instruction (dup, add, etc), so there is no direct variable slot in this case regards, Eugene
message-footer.txt
(text/plain, 238 B)
-- 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