Home/ Questions/Q 5961837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T19:01:19+00:00

Today I was reading up on debugging and I came across a post in

  • 0

Today I was reading up on debugging and I came across a post in stackoverflow saying that the debugger itself in eclipse does not tell alot of useful information and most information lies in the LogCat ?

I’ve done a screenshot of the LogCat output and saw a colorful output which is dazzling. I went ahead with the most obvious danger color (red) and saw that at the end of the output it says error caused by NullpointerException in fillData() and onCreate().

My question is:

  1. Is that an indication of the bug in my code (as mine crashes at startup) ? Is the bug Nullpointerexception ? Is this the right way of finding out immediate bugs in code ?

  2. Is the red color output of Logcat the main portion to zoom in to look for bug problems?

Thank you ! I think this post wud be useful for many noob android coders as there isn’t many resources out there teaching how to use the debugger properly 🙁

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    To view all application logs you should check “LogCat” in “DDMS”.
    In LogCat you can filter logs by Log Level (V=Verbose, D=Debug, I=Info, W=Warning and E=Error).

    You can check application crashes by filtering by Error – this way you can check where the problem is happening (by viewing the stacktrace).

    However, if you want to perform step by step debug, add breakpoints and run the application in debug mode. Then open perspective “Debug” and you’ll be able to debug line by line.

    • 0