Exceptions are trapped by the debugger when they should not be.

This is the bug I sent in a previously marked as
"Not a bug"). I do think there is a problem here. The debugger qualifies as
'uncaught' exceptions which are not explicitely caught, like in:

   try { int i = Integer.parseInt( "one" ); }
   catch( Exception e ){}

TEST CASE
Run JDB on DitherTest. See log:

jdb sun.applet.AppletViewer example1.html
Initializing jdb...
0x14973e8:class(sun.applet.AppletViewer)
> run
run sun.applet.AppletViewer example1.html
running ...
main[1]
sun.applet.AppletViewer exited
main[1]
Uncaught exception: java.lang.NumberFormatException
        at java.lang.Integer.parseInt(Integer.java:145)
        at java.lang.Integer.parseInt(Integer.java:161)
        at DitherTest.colormethod(DitherTest.java:125)
        at DitherTest.init(DitherTest.java:38)
        at sun.applet.AppletPanel.run(AppletPanel.java:259)
        at java.lang.Thread.run(Thread.java:294)

thread applet-DitherTest.class[1] Input stream closed.

COMMENTS (To Thomas Ball)
Thomas, this is the bug I sent you a while ago (which one you marked as
"Not a bug"). I do think there is a problem here. The debugger qualifies as
'uncaught' exceptions which are not explicitely caught, like in:

   try { int i = Integer.parseInt( "one" ); }
   catch( Exception e ){}



      Date: 04/16/1996 09:43 am (Tuesday)
      From: jean-paul buu-sao
        To: UnixDomain.SMTP("###@###.###")
        CC: internet:###@###.###,jbailey,cquinn,gwhite
   Subject: JDK 1.0.2 - Debugger API - Client exit right away

VERSION
JDK 1.0.2 - interim source release, sent by Scott Rautmann on 12/4/96