Intermittent failure from my nightly analysis report:

New nsk.jdb failures (from 2008.10.28)
    nsk/jdb/caught_exception/caught_exception002
        This test failed due to "Debuggee did not exit after 1 <cont>
        commands" on Solaris SPARC-64 Server VM (machine vm-b1600s-5).
        The jdb.session file shows the following interesting snippet:

            main[1] cont
            debugee's main(): caught MyException8
            Set deferred caught nsk.jdb.caught_exception.caught_exception002.MyException9

            Exception occurred: nsk.jdb.caught_exception.caught_exception002.MyException9 (to be caught at: nsk.jdb.caught_exception.caught_exception002.caught_exception002a.a(), line=63 bci=118)"thread=main", nsk.jdb.caught_exception.caught_exception002.caught_exception002a.b(), line=93 bci=155

            main[1] cont
            main[1] debugee's main(): caught MyException9
            > quit

        In the first "cont" command above, the debuggee's output
        about MyException8 comes before the "main[1]" prompt. In
        the second "cont" command above, the debuggee's output
        about MyException9 comes on the same line and after the
        "main[1]" prompt. I wonder if the send/expect logic for
        the jdb infrastructure gets confused here.


Here is a link to the analysis page:

http://sqeweb.sfbay/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-10-28/Serv_Baseline/vm/solaris-sparcv9/server/comp/solaris-sparcv9_server_comp_nsk.jdb.testlist/analysis.html