android – LogCat显示没有

概述这个问题在这里已经有一个答案：            >             LogCat Stops Running in Eclipse Needs Restart                                    10个 我不知道是Android的具体问题还是eclipse相关的问题.我的应用程序工作正常,但经过一段时间后,LogCat显示中止的LogCat-v长,之 这个问题在这里已经有一个答案：> LogCat Stops Running in Eclipse Needs Restart10个
我不知道是AndroID的具体问题还是eclipse相关的问题.我的应用程序工作正常,但经过一段时间后,LogCat显示中止的LogCat-v长,之后不显示任何内容 – 对我来说,日志非常重要 – 任何帮助？

06-13 09:48:42.002: INFO/ActivityThread(219): Publishing provIDer com.androID.email.provIDer: com.androID.email.provIDer.EmailProvIDer    06-13 09:48:42.202: INFO/ActivityThread(219): Publishing provIDer com.androID.email.attachmentprovIDer: com.androID.email.provIDer.AttachmentProvIDer    06-13 09:48:42.722: DEBUG/Exchange(219): BootReceiver onReceive    06-13 09:48:42.871: DEBUG/EAS SyncManager(219): !!! EAS SyncManager,onCreate    06-13 09:48:43.083: INFO/ActivityManager(52): Start proc com.svox.pico for broadcast com.svox.pico/.VoiceDataInstallerReceiver: pID=231 uID=10018 gIDs={}    06-13 09:48:43.522: DEBUG/EAS SyncManager(219): !!! EAS SyncManager,onStartCommand    06-13 09:48:43.632: INFO/ActivityManager(52): displayed activity com.aqui.mwfa/.Mwfa: 5405 ms (total 34831 ms)    06-13 09:48:43.651: DEBUG/ddm-heap(231): Got feature List request    06-13 09:48:43.782: DEBUG/EAS SyncManager(219): !!! EAS SyncManager,stopPing self    06-13 09:48:43.883: DEBUG/Eas DeBUG(219): Logging:     06-13 09:48:43.912: DEBUG/EAS SyncManager(219): !!! EAS SyncManager,onDestroy    06-13 09:48:44.503: DEBUG/dalvikvm(102): GC freed 2862 objects / 157944 bytes in 113ms    06-13 09:48:44.583: DEBUG/MediaScanner(198): opendir /system/media/ Failed,errno: 2    06-13 09:48:44.633: DEBUG/MediaScanner(198):  prescan time: 3125ms    06-13 09:48:44.642: DEBUG/MediaScanner(198):     scan time: 237ms    06-13 09:48:44.652: DEBUG/MediaScanner(198): postscan time: 0ms    06-13 09:48:44.676: DEBUG/MediaScanner(198):    total time: 3362ms    06-13 09:48:44.702: DEBUG/MediaScannerService(198): done scanning volume internal    06-13 09:48:44.742: DEBUG/MediaScannerService(198): start scanning volume external    06-13 09:48:45.031: DEBUG/dalvikvm(52): GREF has increased to 301    06-13 09:48:45.042: VERBOSE/MediaScanner(198): pruneDeadthumbnailfiles... androID.database.sqlite.sqliteCursor@44b75918    06-13 09:48:45.062: VERBOSE/MediaScanner(198): /pruneDeadthumbnailfiles... androID.database.sqlite.sqliteCursor@44b75918    06-13 09:48:45.093: DEBUG/MediaScanner(198):  prescan time: 250ms    06-13 09:48:45.113: DEBUG/MediaScanner(198):     scan time: 7ms    06-13 09:48:45.139: DEBUG/MediaScanner(198): postscan time: 75ms    06-13 09:48:45.142: DEBUG/MediaScanner(198):    total time: 332ms    06-13 09:48:45.154: DEBUG/MediaScannerService(198): done scanning volume external    06-13 09:48:52.001: INFO/ARMAssembler(52): generated scanline__00000077:03545404_00000A04_00000000 [ 29 ipp] (51 ins) at [0x425130:0x4251fc] in 1355035 ns    06-13 09:48:52.091: INFO/ARMAssembler(52): generated scanline__00000177:03515104_00001A01_00000000 [ 73 ipp] (98 ins) at [0x4965a0:0x496728] in 923700 ns    06-13 09:48:52.241: INFO/ARMAssembler(52): generated scanline__00000077:03515104_00000000_00000000 [ 33 ipp] (47 ins) at [0x4951c0:0x49527c] in 529085 ns    06-13 09:48:53.852: INFO/ActivityManager(52): Killing process com.androID.mms (pID=147) at user's request    06-13 09:48:53.861: INFO/Process(52): Sending signal. PID: 147 SIG: 9    06-13 09:48:53.901: INFO/ActivityManager(52): Process com.androID.mms (pID 147) has dIEd.    06-13 09:48:54.052: INFO/ARMAssembler(52): generated scanline__00000177:03515104_00001001_00000000 [ 91 ipp] (114 ins) at [0x495280:0x495448] in 1167970 ns    06-13 09:48:54.061: ERROR/gralloc(52): [unregister] handle 0x43d970 still locked (state=40000001)    06-13 09:48:56.491: INFO/ActivityManager(52): Starting activity: Intent { cmp=com.aqui.mwfa/.Sfa }    06-13 09:48:57.332: DEBUG/dalvikvm(210): GC freed 3003 objects / 224688 bytes in 401ms    06-13 09:48:57.513: DEBUG/request data(210): http://www.aquilonis.net:6789/Aqui-MWFA_p2/mobile:type=getcustomer,uID=49,06-13 09:48:58.412: DEBUG/response data::(210): true#@@#1#@#Abhay Traders#@#3,4#@@#2#@#Abu Traders#@#3,4#@@#3#@#Dhamtari Sales#@#3,4#@@#4#@#Ganesh Traders#@#3,4#@@#5#@#Ganga Sales#@#3,4#@@#6#@#Jyoti Traders#@#3,4#@@#7#@#Krishi Traders#@#3,4#@@#8#@#Manoj Traders#@#3,4    06-13 09:48:58.412: DEBUG/response data::(210): [ 06-13 09:48:58.412   210:0xd2 D/true#@@#1#@#Abhay Traders#@#3,4#@@#4#@#G06-13 09:48:59.291: DEBUG/response data::(210): true#@@#1#@#Abhay [1]   Aborted                 logcat -v long

解决方法 如果在Eclipse中发生这种情况,那么您将需要关闭Eclipse并重新启动它：每次Eclipse中的ADT都会失去与用于显示日志的logcat进程的连接.

如果这是在命令行发生,那么您可能会遇到驱动程序问题：我建议重新安装必要的驱动程序.

总结

以上是内存溢出为你收集整理的android – LogCat显示没有全部内容，希望文章能够帮你解决android – LogCat显示没有所遇到的程序开发问题。

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