android异常,即使jdom库存在

android异常,即使jdom库存在,第1张

概述jdom库在那里,我已经删除并一次又一次地添加到构建路径.而且,我已多次清理该项目.但我仍然得到这个错误:04-2710:51:27.867:W/ActivityThread(530):Applicationcom.pkg.src.nhs.glosiswaitingforthedebuggeronport8100...04-2710:51:27.936:I/System.out(530)

jdom库在那里,我已经删除并一次又一次地添加到构建路径.而且,我已多次清理该项目.但我仍然得到这个错误:

 04-27 10:51:27.867: W/ActivityThread(530): Application com.pkg.src.nhs.glos is waiting for the deBUGger on port 8100...    04-27 10:51:27.936: I/System.out(530): Sending WAIT chunk    04-27 10:51:29.396: I/dalvikvm(530): DeBUGger is active    04-27 10:51:29.736: I/System.out(530): DeBUGger has connected    04-27 10:51:29.746: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:29.996: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:30.262: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:30.479: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:30.689: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:30.896: I/System.out(530): waiting for deBUGger to settle...    04-27 10:51:43.786: D/dalvikvm(553): GC freed 683 objects / 60040 bytes in 110ms    04-27 10:51:49.396: W/dalvikvm(553): VFY: unable to find class referenced in signature (Lcom/AndroidQuery/Aquery;)    04-27 10:51:49.576: W/dalvikvm(553): VFY: unable to find class referenced in signature (Lcom/AndroidQuery/util/XmlDom;)    04-27 10:51:49.646: W/dalvikvm(553): VFY: unable to find class referenced in signature (Lcom/AndroidQuery/callback/AJAXStatus;)    04-27 10:51:49.646: I/dalvikvm(553): Could not find method com.AndroidQuery.util.XmlDom.Tags, referenced from method com.pkg.src.nhs.glos.MainActivity.setimageCallBack    04-27 10:51:49.646: W/dalvikvm(553): VFY: unable to resolve virtual method 80: Lcom/AndroidQuery/util/XmlDom;.Tags (Ljava/lang/String;)Ljava/util/List;    04-27 10:51:49.646: D/dalvikvm(553): VFY: replacing opcode 0x6e at 0x0013    04-27 10:51:49.646: D/dalvikvm(553): Making a copy of Lcom/pkg/src/nhs/glos/MainActivity;.setimageCallBack code (200 bytes)    04-27 10:51:50.126: E/dalvikvm(553): Could not find class 'org.jdom.input.SAXBuilder', referenced from method com.pkg.src.nhs.glos.MainActivity$SetimageTask.doInBackground    04-27 10:51:50.126: W/dalvikvm(553): VFY: unable to resolve new-instance 166 (Lorg/jdom/input/SAXBuilder;) in Lcom/pkg/src/nhs/glos/MainActivity$SetimageTask;    04-27 10:51:50.126: D/dalvikvm(553): VFY: replacing opcode 0x22 at 0x0009    04-27 10:51:50.126: D/dalvikvm(553): Making a copy of Lcom/pkg/src/nhs/glos/MainActivity$SetimageTask;.doInBackground code (205 bytes)    04-27 10:51:50.736: W/dalvikvm(553): threadID=15: thread exiting with uncaught exception (group=0x4001b188)    04-27 10:51:50.746: E/AndroIDRuntime(553): Uncaught handler: thread AsyncTask #1 exiting due to uncaught exception    04-27 10:51:50.846: E/AndroIDRuntime(553): java.lang.RuntimeException: An error occured while executing doInBackground()    04-27 10:51:50.846: E/AndroIDRuntime(553):  at androID.os.AsyncTask.done(AsyncTask.java:200)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.FutureTask.setException(FutureTask.java:124)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.FutureTask.run(FutureTask.java:137)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1068)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.lang.Thread.run(Thread.java:1096)    04-27 10:51:50.846: E/AndroIDRuntime(553): Caused by: java.lang.NoClassDefFoundError: org.jdom.input.SAXBuilder    04-27 10:51:50.846: E/AndroIDRuntime(553):  at com.pkg.src.nhs.glos.MainActivity$SetimageTask.doInBackground(MainActivity.java:100)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at com.pkg.src.nhs.glos.MainActivity$SetimageTask.doInBackground(MainActivity.java:1)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at androID.os.AsyncTask.call(AsyncTask.java:185)    04-27 10:51:50.846: E/AndroIDRuntime(553):  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)    04-27 10:51:50.846: E/AndroIDRuntime(553):  ... 4 more    04-27 10:51:50.941: I/dalvikvm(553): threadID=7: reacting to signal 3    04-27 10:51:50.941: E/dalvikvm(553): Unable to open stack trace file '/data/anr/traces.txt': Permission denIEd    04-27 10:52:02.038: I/Process(553): Sending signal. PID: 553 SIG: 9

解决方法:

检查是否在构建路径设置的“订购和导出”选项卡中选中了jdom库.
如果没有检查,请执行清理并重试运行您的应用程序.

总结

以上是内存溢出为你收集整理的android异常,即使jdom库存在全部内容,希望文章能够帮你解决android异常,即使jdom库存在所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。

欢迎分享,转载请注明来源:内存溢出

原文地址:https://54852.com/web/1109780.html

(0)
打赏 微信扫一扫微信扫一扫 支付宝扫一扫支付宝扫一扫
上一篇 2022-05-29
下一篇2022-05-29

发表评论

登录后才能评论

评论列表(0条)

    保存