dex fails placing debug info

by Michael Newton » Tue, 20 Apr 2010 13:08:24 GMT


Sponsored Links
  hope someone can offer some insight on this problem. My build was
failing with a dex error. After I turned verbosity up to debug I got
the following:

Buildfile: build.xml
[setup] Project Target: Android 1.6
[setup] API level: 4
[setup] WARNING: No minSdkVersion value set. Application will
install on all Android versions.

(snip)

-dex:
[echo] Converting compiled files and external libraries into /
Users/newton/scratch/bin/classes.dex...
[echo]
[apply]
[apply] trouble writing output:
[apply] com.android.dx.util.ExceptionWithContext: shouldn't happen
[apply] at
com.android.dx.util.ExceptionWithContext.withContext(ExceptionWithContext.java:
46)
[apply] at
com.android.dx.dex.file.DebugInfoItem.place0(DebugInfoItem.java:79)
[apply] at
com.android.dx.dex.file.OffsettedItem.place(OffsettedItem.java:241)
[apply] at
com.android.dx.dex.file.MixedItemSection.placeItems(MixedItemSection.java:
312)
[apply] at com.android.dx.dex.file.DexFile.toDex0(DexFile.java:
525)
[apply] at com.android.dx.dex.file.DexFile.toDex(DexFile.java:
196)
[apply] at com.android.dx.command.dexer.Main.writeDex(Main.java:
406)
[apply] at com.android.dx.command.dexer.Main.run(Main.java:143)
[apply] at com.android.dx.command.dexer.Main.main(Main.java:120)
[apply] at com.android.dx.command.Main.main(Main.java:87)
[apply] Caused by: java.lang.RuntimeException: shouldn't happen
[apply] at
com.android.dx.dex.file.DebugInfoEncoder.emitLocalsAtAddress(DebugInfoEncoder.java:
314)
[apply] at
com.android.dx.dex.file.DebugInfoEncoder.convert0(DebugInfoEncoder.java:
220)
[apply] at
com.android.dx.dex.file.DebugInfoEncoder.convert(DebugInfoEncoder.java:
155)
[apply] at
com.android.dx.dex.file.DebugInfoItem.encode0(DebugInfoItem.java:188)
[apply] at
com.android.dx.dex.file.DebugInfoItem.encode(DebugInfoItem.java:144)
[apply] at
com.android.dx.dex.file.DebugInfoItem.place0(DebugInfoItem.java:76)
[apply] ... 8 more
[apply] ...while placing debug info for
com.sshtools.j2ssh.transport.publickey.SshPublicKey.getFingerprint:
()Ljava/lang/String;
[apply] ...while placing
com.android.dx.dex.file.debuginfoi...@55bbe9aa
[apply] ...while writing section 10
[apply]


Here is the source of the class where it is failing to place debug
info:
package com.sshtools.j2ssh.transport.publickey;

import com.sshtools.j2ssh.util.Hash;
import java.security.NoSuchAlgorithmException;

public abstract class SshPublicKey {

public abstract String getAlgorithmName();

public abstract int getBitLength();

public abstract byte[] getEncoded();

public String getFingerprint() {
try {
Hash md5 = new Hash("MD5");
md5.putBytes(getEncoded());

byte[] digest = md5.doFinal();
int bits = getBitLength();
bits = (((bits % 8) != 0) ? (bits += (bits % 8)) : bits);

String ret = String.valueOf(bits);

for (int i = 0; i < digest.length; i++) {
ret += (((i == 0) ? ":" : "") + " " +
Integer.toHexString(digest[i] & 0xFF));
}

return ret;
} catch (NoSuchAlgorithmException nsae) {
return null;
}
}

publ



dex fails placing debug info

by Dan Bornstein » Wed, 21 Apr 2010 07:33:11 GMT


 On Mon, Apr 19, 2010 at 4:26 PM, Michael Newton



This looks like a bug in dx (the tool that turns .class files into
.dex files). Since compilers can produce different output for the same
source, it's much more interesting to see the compiled .class file
that is being processed.

Please file a bug by following the directions at
< http://source.android.com/report-bugs> ;. Again, in this case,
attaching the .class file that fails is much better than just
including the source text.

As a workaround, you might try compiling without debugging info (that
is, removing "-g" from your javac command line). You might also try
splitting the failing method (getFingerPrint) in various places (e.g.,
put the try body in a separate method), as that will change the
emitted code and has a good chance of avoiding the problem.

Cheers,

-dan

--


Sponsored Links


dex fails placing debug info

by Michael Newton » Wed, 21 Apr 2010 23:26:17 GMT


 I fixed this - this code is where the problem is:

            int bits = getBitLength();
            bits = (((bits % 8) != 0) ? (bits += (bits % 8)) : bits);

When I assigned the result of the expression in the second line to a
new variable instead of back to int bits, the problem went away.

The clue was in  http://code.google.com/p/android/issues/detail?id=2868 
- may be the same kind of issue.

M.




>



dex fails placing debug info

by fadden » Fri, 23 Apr 2010 04:10:41 GMT


 



Can you attach the failing and non-failing .class files to that bug?

--



Other Threads

1. Not able to find adb.exe

Hi all,
I am new to Android. I have downloaded all the SDK Components from SDK
Installer. I am using ecllipse Ganymede. Also, I have installed
ADT-10.0.1 in ecllipse. But when I browse my sdk location in Window >
Preferences > Android, it is showing error as 'Could not find adb.exe
in Adroid-SDK\tools\'. In my Android sdk, adb.exe is located inside
'Android-SDK\platform-tools\' directory. How can I able to change this
adb.exe file path? I have included Android-SDK\platform-tools\
directory in PATH variable.
Anybody please help me out.

Cheers,
 Yogi

-- 

2. in app billing: PURCHASE_STATE_CHANGED sends empty orders

Dear list,

in 5-10% of all purchases, my BillingReceiver (basically taken from
the dungeons sample) gets a PURCHASE_STATE_CHANGED notification with
empty orders list:

05-08 17:15:17.294 D/BillingReceiver(13171)purchaseStateChanged:
{"nonce":4596323482244846986,"orders":[]}

The BillingService does not confirm this notification because that
code is never reached when orders is empty, but immediately I get a
RESPONSE_CODE with RESULT_OK.

The net result is that the user pays money but the app doesn't give
him anything for it, because it cannot process any order from an empty
list using BillingResponseHandler.purchaseResponse(). This is
obviously a bad thing.

The purchased item is in all known cases a non-managed in app product.

Is this known? Am I doing something wrong? How shall I handle this
case?

Thanks

Uwe

-- 

3. Phone crash on volume key

4. Mixing of voice

5. RatingBar

6. Segmentation fault when loading a certain class from an OSGi framework under Android 2.2 & 2.3

7. C Sharp Basics