GVKun编程网logo

android断点错误eclipse(eclipse 断点source not found)

2

本文将分享android断点错误eclipse的详细内容,并且还将对eclipse断点sourcenotfound进行详尽解释,此外,我们还将为大家带来关于(OK—C程序)EclipseC/C++—C

本文将分享android断点错误eclipse的详细内容,并且还将对eclipse 断点source not found进行详尽解释,此外,我们还将为大家带来关于( OK—C程序 ) Eclipse C/C++ — CentOS 7 + android-ndk + eclipse-cpp-mars-R、Android eclipse 断点调试、android eclipse中的Android直接運行java main方法、Android Eclipse无法启动.发生了错误.看日志文件的相关知识,希望对你有所帮助。

本文目录一览:

android断点错误eclipse(eclipse 断点source not found)

android断点错误eclipse(eclipse 断点source not found)

在 Eclipse上调试 Android应用程序时,在选择“Resume”(F8)之后,代码会在代码编辑器中打开的某些Android系统类中随机停止(尽管它们缺少源代码),如ZygoteInit或其他类.

还有其他人经历过这个吗?我怎样才能解决这个问题?

解决方法

当您的应用因未捕获的异常而崩溃时,通常会发生这种情况.如果再次点击恢复,它会将错误吐出到logcat. Eclipse中可能有一些设置不能自动打开没有源的文件,或者在异常时没有自动停止,但我刚刚停止使用eclipse.

( OK—C程序 ) Eclipse C/C++ — CentOS 7 + android-ndk + eclipse-cpp-mars-R

( OK—C程序 ) Eclipse C/C++ — CentOS 7 + android-ndk + eclipse-cpp-mars-R

ftp://ftp.bluage.com/eclipse45/eclipse-cpp-mars-R-linux-gtk-x86_64.tar.gz
ftp://ftp.bluage.com/eclipse45/eclipse-cpp-mars-R-win32-x86_64.zip

CentOS 7  +  android-ndk-r10d-linux-x86_64.bin  +  eclipse-cpp-luna-SR2-linux-gtk-x86_64.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------  compile c  ------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
eclipse的设置如下:

Tool Chain Editor:
  Debug [Active]
  Cross GCC
  Gnu Make Builder
  Used tools:
    Cross GCC Compiler
    Cross G++ Compiler
    Cross GCC Linker
    Cross G++ Linker
    Cross GCC Archiver
    Cross GCC Assembler


cross settings:
arm-linux-androideabi-
/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64

cross gcc compiler:

Include paths(-I):
/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/include
/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/include
/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9/include-fixed
/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9/include

Miscellaneous: --->
other flags: -c -fmessage-length=0 -DANDROID -fno-exceptions
勾选: -fPIC

cross gcc linker:
all options:  -nostdlib -L/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/
general:  -nostdlib

Libraries:
(-l)  c
(-L)  /opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/

Miscellaneous:
Other options:
-R/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib
Other objects:
/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/crtbegin_dynamic.o
/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/crtend_android.o


+++++++++++ eclipse编译过程
09:09:30 **** Incremental Build of configuration Debug for project helloworldc ****
make all
Building file: ../src/helloworldc.c
Invoking: Cross GCC Compiler
arm-linux-androideabi-gcc -I/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/include -I/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/include -I/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9/include-fixed -I/opt/android-on-linux/android-ndk-r10d/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9/include -O0 -g3 -Wall -c -fmessage-length=0 -DANDROID -fno-exceptions -fPIC -MMD -MP -MF"src/helloworldc.d" -MT"src/helloworldc.d" -o "src/helloworldc.o" "../src/helloworldc.c"
Finished building: ../src/helloworldc.c
 
Building target: helloworldc
Invoking: Cross GCC Linker
arm-linux-androideabi-gcc -nostdlib -L/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/ -Xlinker -R/opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib -o "helloworldc"  ./src/helloworldc.o  /opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/crtbegin_dynamic.o /opt/android-on-linux/android-ndk-r10d/platforms/android-21/arch-arm/usr/lib/crtend_android.o -lc
Finished building target: helloworldc
 

09:09:32 Build Finished (took 1s.269ms)

+++++++++++++++

++++++++ 在CentOS 7
[root@localhost helloworldc]# pwd
/opt/eclipse-workspace/helloworldc
[root@localhost helloworldc]# ls
Debug  src
[root@localhost Debug]# pwd
/opt/eclipse-workspace/helloworldc/Debug
[root@localhost Debug]# ls
helloworldc  makefile  objects.mk  sources.mk  src
[root@localhost Debug]# adb push helloworldc /data/data/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
718 KB/s (30436 bytes in 0.041s)
[root@localhost Debug]#

+++++++++ Android (ARM)
[root@localhost Debug]# adb root
[root@localhost Debug]# adb shell
root@mb526:/ # cd data/data
root@mb526:/data/data # ./helloworldc                                       
!!!Hello World!!!



Android eclipse 断点调试

Android eclipse 断点调试

1、直接右键项目Debug As->Android Application以调试模式的方式运行应用;

2、点击代码左边空白处如图中红圈处添加断点:

3、运行代码,eclipse如下:

如上图运行代码后会进入debug模式,图中:

  1. 标注1表示:运行时的代码栈,第一行显示当前调试代码在哪一行,每行的下一行表示跳到此行的地方。

  2. 标注2表示:调试过程中的一些变量的值。同时也可以把鼠标移到标注7中变量上显示变量的值。

  3. 标注3表示:此时代码中断点的个数及位置信息等,单击右键可以remove,remove all等。

  4. 标注4表示:执行流程直接跳到下个断点处。

  5. 标注5表示:退出debug模式,正常执行程序。

  6. 标注6中:第1个图标表示跟踪跳入此行中的方法中,第2个便是按照顺序执行下一行,图标3跳出第1个图标进入的方法。

  7. 标注7表示:正在执行的代码,在调试的过程中可以把鼠标移到变量上跟踪变量的值。


其实断点调试没什么难的,知道这些基本够用了!


android eclipse中的Android直接運行java main方法

android eclipse中的Android直接運行java main方法

       在Android项目中实现Socket通信,服务器端使用main方法创建ServerSocket,运行启动服务器时报错“Error: ShouldNotReachHere() ”。
原因分析:java中使用main函数作为应用程序的接口,class的生命周期始于main方法,终于main方法。Android虽然使用的是java语法,但是却不使用main作为程序入口,一个activity启动时要经过onCreate()方法、onStart()方法和onResume()方法才算完全启动,而且这些方法都是自动调用的,这是与java application运行的最大不同处。所以如果你新建的是Android Project,那么程序默认使用的就是android.jar来作为程序运行时环境,但是由于我们按照惯例将服务器端ServerSocket的启动放在main方法中,android无法解析,所以会报出“Error: ShouldNotReachHere() ”错误,就是说程序永远不会执行到这里,这种错误平时也常见,比如说你在定义了一条return语句后又在后面加上一句System.out.println("xxxx")一样,return表示程序已经结束,后面那句System是永远无法执行的,因为按照java语法程序无法被解析。
    解决方案一:隔离服务器端和客户端。将服务器端ServerSocket的创建移到Android项目之外的一个Java Project中,先运行这个Java Project,启动ServerSocket,再运行客户端所在的Android Project。
    解决方案二:更改服务器端运行时环境。将ServerSocket依旧写在Java类中的main方法中,在IDE左边的Package Exployer中选中项目,点击鼠标右键,选择“Run as——>Run configuration”,在弹出窗口的左边框内找到“Java application——>ServerSocket类”,在右边框内找到Classpath选项,找到其中的Bootstrap Entries,选中其中的android.jar,点击右边remove按钮将其删除,然后点击Advanced按钮,选择Add Libaby选项,点击ok按钮,在弹出的对话框中选择JRE System Library,点击“next”按钮,选择Workplace Default JRE选项,点击“finish”按钮即可完成配置。
    解决方案三:使用Android中的Activity创建服务器ServerSocket。这种方案应该将服务器和客户端都写在同一个Activity中的不同方法中,先启动服务器方法,再启动客户端方法。这是因为Android中一个Activity就代表了一个屏幕,如果你将服务器和客户端写在不同的Activity中,先启动服务器Activity,再跳转到客户端Activity,那么服务器Activity就会执行onPause()回调方法,相当于关闭Socket服务器了。
解决方案四:使用Android中的Service创建服务器ServerSocket。创建一个Service用来存放Socket服务器代码,再创建一个Activity来存放Socket客户端代码和显示通信信息。运行时先通过Activity启动Service,再启动客户端代码的Activity。由于Android中的Service是后台运行,所以即使跳转Activity也不会关闭服务。
    这四种方案中,第一种将服务器和客户端分隔在不同项目中,不利于管理;第三种方案将客户端和服务器代码写在同一个类中,显得杂乱而且不符合实际情况。个人觉得可取的是第二种和第四种方案,特别是第四种方案。第二种方案夹杂了Android和Java环境处理,第四种方案则是纯粹的Android应用,而且用到了Android中的Service,“Service——Activity”更符合Socket的“服务器——客户端”模式。
 
以上文章是從網絡上搜索出來的,本人已經測試了第二種方案,可以通過;
具體做法就是:
(1)右鍵 入口類(含有Main方法的)==>Run Configurations==>雙擊(Java Application)==>New==>
(2)在標籤Main里選好相應的ProjectName和要運行ClassName,
(3)選標籤ClassPath中的Bootstrap Entries ,再從右邊點 Advance==>Add Library==>JRE System Library,完成,然後將 JRE System Library 點中再點 Up按鈕,OK了

Android Eclipse无法启动.发生了错误.看日志文件

Android Eclipse无法启动.发生了错误.看日志文件

我知道StackOverflow(以及其他人)已多次询问过这个问题,但我发现的解决方案都不适用于我.

正如您在标题中看到的那样,我在启动Android eclipse时收到以下错误消息:

an error has occurred. see the log file

我试过从eclipse.ini文件中删除SNAP文件和Vmargs指令.我还尝试使用以下命令清理Eclipse:

PATH/TO/ECLIPSE -clean

但没有结果.

我在Windows 7上运行ADT Eclipse软件包.

这是我的日志文件(重复)在我尝试运行它时所说的内容:

!ENTRY org.eclipse.core.resources 4 2 2014-05-26 13:45:14.494 !MESSAGE
Problems occurred when invoking code from plug-in:
“org.eclipse.core.resources”. !STACK 0 java.lang.NullPointerException
at
org.eclipse.ui.activities.WorkbenchActivityHelper.isFiltering(WorkbenchActivityHelper.java:235)
at
org.eclipse.ui.internal.ide.IDEWorkbenchActivityHelper$3.resourceChanged(IDEWorkbenchActivityHelper.java:158)
at
org.eclipse.core.internal.events.notificationmanager$1.run(notificationmanager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at
org.eclipse.core.internal.events.notificationmanager.notify(notificationmanager.java:285)
at
org.eclipse.core.internal.events.notificationmanager.broadcastChanges(notificationmanager.java:149)
at
org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
at
org.eclipse.core.internal.events.AutoBuildJob.dobuild(AutoBuildJob.java:156)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

这就是它在上次关闭eclipse之前/之前写的最后一件事:

!ENTRY org.eclipse.ui.workbench 4 0 2014-05-25 21:37:47.323
!MESSAGE An unexpected exception was thrown.
!STACK 0
java.lang.NullPointerException
    at org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1232)
    at org.eclipse.ui.internal.Workbench.getActiveWorkbenchWindow(Workbench.java:1225)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActiveShell(WorkbenchSourceProvider.java:924)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:133)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:684)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.display.filterEvent(display.java:1262)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
    at org.eclipse.swt.widgets.decorations.WM_ACTIVATE(decorations.java:1664)
    at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:2145)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4525)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.decorations.windowProc(decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.display.windowProc(display.java:4976)
    at org.eclipse.swt.internal.win32.OS.BringWindowToTop(Native Method)
    at org.eclipse.swt.widgets.decorations.bringToTop(decorations.java:231)
    at org.eclipse.swt.widgets.Shell.open(Shell.java:1217)
    at org.eclipse.jface.window.Window.open(Window.java:797)
    at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
    at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
    at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
    at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
    at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
    at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
    at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:108)
    at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
    at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
    at org.eclipse.ui.internal.JFaceUtil$3.show(JFaceUtil.java:70)
    at org.eclipse.jface.util.SafeRunnable.handleException(SafeRunnable.java:67)
    at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
    at org.eclipse.ui.internal.Workbench.fireWindowClosed(Workbench.java:948)
    at org.eclipse.ui.internal.WorkbenchWindow.fireWindowClosed(WorkbenchWindow.java:1255)
    at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1177)
    at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1136)
    at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1197)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1195)
    at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1207)
    at org.eclipse.ui.internal.WorkbenchWindow$6.close(WorkbenchWindow.java:445)
    at org.eclipse.e4.ui.workbench.renderers.swt.WBWrenderer$11.shellClosed(WBWrenderer.java:580)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
    at org.eclipse.swt.widgets.decorations.closeWidget(decorations.java:309)
    at org.eclipse.swt.widgets.decorations.WM_CLOSE(decorations.java:1694)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4530)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.decorations.windowProc(decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.display.windowProc(display.java:4976)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
    at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.decorations.windowProc(decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.display.windowProc(display.java:4976)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
    at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.decorations.windowProc(decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.display.windowProc(display.java:4976)
    at org.eclipse.swt.internal.win32.OS.dispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.dispatchMessage(OS.java:2546)
    at org.eclipse.swt.widgets.display.readAnddispatch(display.java:3756)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(UnkNown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(UnkNown Source)
    at java.lang.reflect.Method.invoke(UnkNown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
!SESSION 2014-05-26 13:23:08.484 -----------------------------------------------
eclipse.buildId=v22.3.0-887826
java.version=1.7.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=win32,ARCH=x86_64,WS=win32,NL=en_US
Framework arguments:  -product com.android.ide.eclipse.adt.package.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.android.ide.eclipse.adt.package.product

我真的希望你们中的一些人可以帮我解决这个问题.
我最后一次关闭Android eclipse时出现了一些问题,因为它内存不足.我不知道为什么突然发生了这件事.

解决方法

当然,在发布问题之后,我找到了解决方案.

如果其他人遇到同样的问题,请尝试从工作区中删除以下文件夹:

C:\.. \workspace\.Metadata\.plugins\org.eclipse.e4.workbench

关于android断点错误eclipseeclipse 断点source not found的问题就给大家分享到这里,感谢你花时间阅读本站内容,更多关于( OK—C程序 ) Eclipse C/C++ — CentOS 7 + android-ndk + eclipse-cpp-mars-R、Android eclipse 断点调试、android eclipse中的Android直接運行java main方法、Android Eclipse无法启动.发生了错误.看日志文件等相关知识的信息别忘了在本站进行查找喔。

本文标签: