do not compute frames in ClassWriter
do not compute frames in ClassWriter

Computed frames in instrumentation output may only positively affect the speed
of class verification, but computing it (a) is costly, (b) is nontrivial in case
some classes are not loaded, i.e. classWriter.getCommonSuperClass() tries to
load classes too eagerly and gets confused.

fixes bug: http://code.google.com/p/data-race-test/issues/detail?id=30


XQQ8765/java-thread-sanitizer,google/java-thread-sanitizer,XQQ8765/java-thread-sanitizer,google/java-thread-sanitizer,fengshao0907/java-thread-sanitizer,fengshao0907/java-thread-sanitizer