You can try to compile in the command-line, since you prefer it. In the IDE, Xavier's suggestion is one good way. Also if you look at the source tree, you will see a red x on the problem branch. Expand that branch to find where the culprit file is.
Yusuf Saib Android ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Jul 23, 2:52 pm, Xavier Ducrohet <[email protected]> wrote: > The compilations errors are displayed in a view called "Problems". It > should be in the same tab group as Console. > > The "Error Log" view is for error related to the plug-ins running in eclipse. > > Xav > > > > > > On Wed, Jul 22, 2009 at 8:12 PM, James<[email protected]> wrote: > > > I'm not much a fan of GUI IDE's like Eclipse, but it's harder to debug > > without it. :-( > > > I have a project that compiles and loads fine using ant (via make); no > > compile errors. The trouble is that it doesn't quite work correctly, > > and it'd be nice to get some runtime debug info like you can get using > > Eclipse and its adb interface. > > > The trouble is that when I try to run it in Eclipse/Debug (F11) a > > popup box says "You have errors in your application, please fix them > > before running." > > > But how do I find these errors? There is no useful information in the > > Console or Error Log. Or if someone can parse the Error.log entry > > below, please > > help! None of the files have little red X's indicative of a problem. > > And the program runs (but doesn't work) outside of Eclipse. > > > Or is there a way I can debug (and query runtime variables) without > > using Eclipse? > > > Thanks ! > > > Jim > > > (This is my second attempt at posting; the first didn't seem to show > > up. But if you see it twice, my apologies.) > > ------------------ > > eclipse.buildId=I20090611-1540 > > java.version=1.6.0_14 > > java.vendor=Sun Microsystems Inc. > > BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US > > Framework arguments: -product org.eclipse.epp.package.java.product > > Command-line arguments: -os linux -ws gtk -arch x86 -product > > org.eclipse.epp.package.java.product > > > !ENTRY org.eclipse.help.ui 4 0 2009-07-22 14:34:18.359 > > !MESSAGE There was an error executing the command: > > org.eclipse.debug.ui.commands.OpenDebugConfigurations > > !STACK 0 > > org.eclipse.core.commands.NotHandledException: There is no handler to > > execute for command > > org.eclipse.debug.ui.commands.OpenDebugConfigurations > > at org.eclipse.core.commands.Command.executeWithChecks > > (Command.java: > > 485) > > at > > org.eclipse.core.commands.ParameterizedCommand.executeWithChecks > > (ParameterizedCommand.java:508) > > at > > org.eclipse.help.ui.internal.ExecuteCommandAction.executeSerializedCommand > > (ExecuteCommandAction.java:115) > > at org.eclipse.help.ui.internal.ExecuteCommandAction.access$1 > > (ExecuteCommandAction.java:110) > > at org.eclipse.help.ui.internal.ExecuteCommandAction$2.run > > (ExecuteCommandAction.java:76) > > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java: > > 35) > > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages > > (Synchronizer.java:134) > > at org.eclipse.swt.widgets.Display.runAsyncMessages > > (Display.java: > > 3468) > > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java: > > 3115) > > at org.eclipse.ui.internal.Workbench.runEventLoop > > (Workbench.java: > > 2405) > > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) > > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java: > > 2221) > > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) > > at org.eclipse.core.databinding.observable.Realm.runWithDefault > > (Realm.java:332) > > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench > > (Workbench.java:493) > > at org.eclipse.ui.PlatformUI.createAndRunWorkbench > > (PlatformUI.java: > > 149) > > at org.eclipse.ui.internal.ide.application.IDEApplication.start > > (IDEApplication.java:113) > > at org.eclipse.equinox.internal.app.EclipseAppHandle.run > > (EclipseAppHandle.java:194) > > 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:368) > > at org.eclipse.core.runtime.adaptor.EclipseStarter.run > > (EclipseStarter.java:179) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke > > (NativeMethodAccessorImpl.java:39) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke > > (DelegatingMethodAccessorImpl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:597) > > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: > > 559) > > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) > > at org.eclipse.equinox.launcher.Main.run(Main.java:1311) > > -- > Xavier Ducrohet > Android Developer Tools Engineer > Google Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
