ILOGV("|move%s v%d,v%d %s(v%d=0x%08x)",(INST_INST(inst) == OP_MOVE) ? "" : "-object", vdst, vsrc1,
kSpacing, vdst, GET_REGISTER(vsrc1));
If you enable those ILOGV statement, you are going to get an insane amount of log spam. Every process on the device is going to print a message to logcat for every dalvik instruction that is executed.
If I were doing this, I would take a different approach. I would extract the dex file from the process, using something like ptrace, and then run baksmali on it.
But if you really do want to enable that, it's easy to find where
ILOGV is defined. As you can see,
ILOGV is only enabled if the
LOG_INSTR symbol is defined. Another quick search shows a handy #define statement for
LOG_INSTR earlier in the file that is commented out.
It looks like you should be able to uncomment that and recompile dalvik in order to generate the insanely massive amounts of logspam that you seem to want.
Keep in mind that dalvik has different interpreters. The portable c interpreter, and arch specific interpreters, etc. So you'll need to be aware of which interpreter is being used on your device, and make sure to modify the correct one -- or just modify all them. E.g. by modifying the common header.cpp and running rebuild.sh to regenerate the various interpreters.