diff options
| author | Andy McFadden <fadden@android.com> | 2010-11-11 16:49:22 -0800 |
|---|---|---|
| committer | Andy McFadden <fadden@android.com> | 2010-11-12 08:01:27 -0800 |
| commit | a0929372ae4996cde3aece52f98128a957166ffc (patch) | |
| tree | 2d6f810ff200c5a2812a7618beb66eb06d648a06 /dexdump | |
| parent | edb7b25cb23f40d93b11e77ae5549a676bdea7b8 (diff) | |
| download | android_dalvik-a0929372ae4996cde3aece52f98128a957166ffc.tar.gz android_dalvik-a0929372ae4996cde3aece52f98128a957166ffc.tar.bz2 android_dalvik-a0929372ae4996cde3aece52f98128a957166ffc.zip | |
Stop reporting negative widths.
At one point, returning a negative width for dexopt output was useful.
That stopped being the case a long time ago.
This also removes a bad assert that went into my previous checkin.
Change-Id: I18880c2316f5499a09dc479d271ca70b2a5be259
Diffstat (limited to 'dexdump')
| -rw-r--r-- | dexdump/DexDump.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/dexdump/DexDump.c b/dexdump/DexDump.c index 4fb3878c9..26bb07bb0 100644 --- a/dexdump/DexDump.c +++ b/dexdump/DexDump.c @@ -1089,7 +1089,7 @@ void dumpBytecodes(DexFile* pDexFile, const DexMethod* pDexMethod) insnWidth = 4 + ((size * width) + 1) / 2; } else { opCode = instr & 0xff; - insnWidth = dexGetInstrWidthAbs(gInstrInfo.widths, opCode); + insnWidth = dexGetInstrWidth(gInstrInfo.widths, opCode); if (insnWidth == 0) { fprintf(stderr, "GLITCH: zero-width instruction at idx=0x%04x\n", insnIdx); |