Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 10BFBDAA4 for ; Fri, 10 Aug 2012 10:45:38 +0000 (UTC) Received: (qmail 71513 invoked by uid 500); 10 Aug 2012 10:45:38 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 71175 invoked by uid 500); 10 Aug 2012 10:45:31 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 71125 invoked by uid 99); 10 Aug 2012 10:45:29 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2012 10:45:29 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 57010141E20 for ; Fri, 10 Aug 2012 10:45:29 +0000 (UTC) Date: Fri, 10 Aug 2012 10:45:29 +0000 (UTC) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Message-ID: <18107818.79.1344595529362.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (DERBY-4458) Dalvik / Andoid compatibility MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4458?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1343= 2691#comment-13432691 ]=20 Kristian Waagan commented on DERBY-4458: ---------------------------------------- As for generating .dex files there's now http://code.google.com/p/dexmaker/= . Other potential libs are smali and asmdex, but no idea how well suited t= hey are. Anyone up for making the byte-code generation in Derby pluggable? ;) On a similar note, but unrelated to Android, would it be better if we used = ASM to generate the byte-code? =20 > Dalvik / Andoid compatibility > ----------------------------- > > Key: DERBY-4458 > URL: https://issues.apache.org/jira/browse/DERBY-4458 > Project: Derby > Issue Type: Improvement > Components: Miscellaneous > Affects Versions: 10.5.3.0 > Environment: dx 1.2 (from the Android SDK 2.0) running on Java 1.= 6 > Reporter: Thomas G=C3=B6rres > > derby.jar cannot be used on mobile devices running the Android OS. Androi= d uses Dalvik as runtime environment, and the classfiles from derby.jar can= not be translated to Dalvik byte code. > Steps to repeat: > 1. get the Android SDK from http://developer.android.com > 2. navigate to [android-sdk]/platforms/android-1.5/tools > 3. execute ./dx --dex path/to/derby.jar > The dx tool should convert the JRE byte code to Dalvik byte code. Instead= , it spits out this warning several time: > warning: Ignoring InnerClasses attribute for an anonymous inner class tha= t doesn't come with an associated EnclosingMethod attribute. (This class wa= s probably produced by a broken compiler.) > Then it runs out of memory: > java.lang.OutOfMemoryError: Java heap space > =09at com.android.dx.rop.code.ThrowingInsn.withNewRegisters(ThrowingInsn.= java:116) > =09at com.android.dx.ssa.NormalSsaInsn.toRopInsn(NormalSsaInsn.java:122) > =09at com.android.dx.ssa.back.SsaToRop.convertInsns(SsaToRop.java:386) > =09at com.android.dx.ssa.back.SsaToRop.convertBasicBlock(SsaToRop.java:36= 5) > =09at com.android.dx.ssa.back.SsaToRop.convertBasicBlocks(SsaToRop.java:3= 00) > =09at com.android.dx.ssa.back.SsaToRop.convertToRop(SsaToRop.java:277) > =09at com.android.dx.ssa.back.SsaToRop.convert(SsaToRop.java:118) > =09at com.android.dx.ssa.back.SsaToRop.convertToRopMethod(SsaToRop.java:7= 1) > =09at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:103) > =09at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:74) > =09at com.android.dx.dex.cf.CfTranslator.processMethods(CfTranslator.java= :269) > =09at com.android.dx.dex.cf.CfTranslator.translate0(CfTranslator.java:131= ) > =09at com.android.dx.dex.cf.CfTranslator.translate(CfTranslator.java:85) > =09at com.android.dx.command.dexer.Main.processClass(Main.java:297) > =09at com.android.dx.command.dexer.Main.processFileBytes(Main.java:276) > =09at com.android.dx.command.dexer.Main.access$100(Main.java:56) > =09at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:228) > =09at com.android.dx.cf.direct.ClassPathOpener.processArchive(ClassPathOp= ener.java:245) > =09at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener= .java:130) > =09at com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.ja= va:108) > =09at com.android.dx.command.dexer.Main.processOne(Main.java:245) > =09at com.android.dx.command.dexer.Main.processAllFiles(Main.java:183) > =09at com.android.dx.command.dexer.Main.run(Main.java:139) > =09at com.android.dx.command.dexer.Main.main(Main.java:120) > =09at com.android.dx.command.Main.main(Main.java:87) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira