[27064] in Athena Bugs

home help back first fref pref prev next nref lref last post

Re: sun4 9.4.36: java 1.5.0_06's jdb

daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Sun Mar 11 00:03:55 2007

To: John Hawkinson <jhawk@mit.edu>
From: Jacob Morzinski <morzinski@mit.edu>
Date: Sun, 11 Mar 2007 00:03:42 -0500
In-Reply-To: <bugs:27062@unknown-discuss-server> (John Hawkinson's message
	of "Sat, 10 Mar 2007 22:15:25 -0500")
Message-ID: <w6mbqj0qslt.fsf@horobi.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Flag: NO
X-Spam-Score: 0.00
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu


Hi,

I can offer some commentary: in testing, I can successfully set
breakpoints if I "stop in Test.main" or if I "stop at Test:4".
JDB prints some diagnostics in these cases:
  "VM Started: Set deferred breakpoint Test.main"

I cannot use "step" to enter the java.io.PrintStream.println
method. ("System.out" is a field which holds a PrintStream object).
Perhaps the characteristic which prevents stepping into it also
prevents setting a breakpoint on it.

 -Jacob


John Hawkinson <jhawk@mit.edu> writes:
> What's wrong:
> 	In short, jdb exits when my application exits, and ignores
> 	breakpoints. For example:
>
> What should have happened:
> 	jdb should have stopped at the breakpoint. It also should not
> 	have terminated when the app terminated.
>
> 	I see the same problem under Linux.


home help back first fref pref prev next nref lref last post