3

I am using a jdb dubugger, and the problem with it that is stops on every caught exception, though I did not execute any catch .... statements. During class loading there are hundreds of them:

Exception occurred: java.io.FileNotFoundException (uncaught)"thread=Thread-2-EmulatorEngine", sun.misc.URLClassPath$JarLoader.ensureOpen(), line=634 bci=30

Is it any way to instruct jdb to skip these exceptions ?

PS. I have heard about IDE editors of cause. Have reasons to use jdb.

Nulldevice
  • 3,926
  • 3
  • 31
  • 37

2 Answers2

5

I realized that I am not careful enough. JDB writes after launch these lines

Set uncaught java.lang.Throwable

Set deferred uncaught java.lang.Throwable

So, to disable that, I need to enter a command

ignore uncaught java.lang.Throwable
Community
  • 1
  • 1
Nulldevice
  • 3,926
  • 3
  • 31
  • 37
  • 3
    Not found: uncaught java.lang.Throwable Usage: ignore [uncaught|caught|all] | When running jdb App.class, would anybody have any ideas? – 64k Aug 05 '17 at 22:40
-1

If you're having the same issue as me, you need to use the fully qualified name of the class when defining the break point.

Example - Set break point in main method: stop in com.foo.bar.App.main

It may be that you are trying to set a break point for a class file different than the one you are debugging (which probably doesn't exist).