Re: Data and control flow analysis

Hi,

obviously the following verifier call leads to a non instrumented inner
class sometimes. I fixed a little bug in my instrumentation code. The
example from my previous mail now works properly. But in a more complex
scenario I still have a problem. If I add a call to the internal asm
verifier the inner class is just not instrumented. If I leave it out,
the example works - i.e. the Java verifier obviously does not have any
problems with the bytecode. Any ideas where this bug might come from?

// add byte code verifier
StringWriter stringWriter = new StringWriter();
CheckClassAdapter.verify(new ClassReader(classWriter.toByteArray()),
false, new PrintWriter(stringWriter));
         if (stringWriter.getBuffer().length() > 0) {
            logger.severe(stringWriter.toString());   
         }


Nikolas
Am So 12.12.2010 13:11 schrieb Nikolas Nehmer
<[email protected]>:

>Hi,
>
>is there any good bytecode-based data and control flow analysis tool
>out
>there - intra- and interprocedural? For every variable assignment in an
>application I need to answer several questions. What is scope of this
>modification (i.e. visibility), e.g. does potentially exist a reference
>to the object of the current instance variable modification outside of
>the current component? Is this modification the first one on this
>specific variable and object within the current component? Similar
>questions have to be answered for class and local variable assignments.
>
>The more I'm able to answer these questions statically by code
>analysis,
>the better the performance of my approach or tool gets.
>
>Any suggestions?
>
>Best regards
>Nikolas
>

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