Article View: borland.public.jbuilder.debugger
Article #5194Re: Inspecting variables in Java/AWT code
From: Richard Wilkman
Date: Thu, 02 Jul 1998 00:00
Date: Thu, 02 Jul 1998 00:00
64 lines
2766 bytes
2766 bytes
Greg: You whiner! Now I'll make sure to work my evil to block you from getting this for another release! ;-) You can still trace into it, which is what I'd bet most folks use it for. -Rich Greg Hamer wrote: > > The java stuff and jbcl are not delivered with debug info. You can > re-compile them yourself with the debug flag turned on. I am amazed that > more people do not scream about this. > > Prakash Manghnani wrote: > > > Hi All, > > > > Well, I just got JBuilder2.0. > > > > The debugger is driving me nuts. > > > > One of the things I would like to be able to do is single step into JDK > > source code, and inspect various variables. > > As long as I am in my code, I can view/inspect variables. > > As soon as I step into any java.xxx class, I just cant view any > > variable. > > > > I looked at the View/DebuggerContextBrowser window. Still no-can-do. > > Also I am using just the Borland_Jdk1.1.6 (nothing exotic like switching > > JDK's). > > > > This seems to be basic debugger functionality. I have it working in both > > VisualJ++ and Symantic Cafe. > > I dont know if this is just some "well hidden" option that can be > > re-enabled, or if this JBuilder2 is a pre-alpha quality product. > > So, unless this problem can be resolved, I'm back to VisualJ++ (sob). > > > > Any help would be appreciated. > > > > -- > > -------------------------------------------------------------------- > > Prakash Manghnani > > Industech > > E-mail: prakash@industech.com > > -------------------------------------------------------------------- -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rich Wilkman Senior Quality Assurance Engineer Borland JBuilder Team If you see something that looks like an opinion up there, it's mine and mine alone. Mail sent to me from the newsgroups won't bounce but will be ignored. If I have time, I'll respond, but you have a better chance if you confine your posts to the newsgroups =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Technical Details
Message-ID:
<359BA634.24E932AD@inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<35773EF2.6005@industech.com> <359AD644.F7E2C0AC@inprise.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5c5,ad7fd6825ab08286 X-Google-Attributes: gidff5c5,public X-Google-Thread: fa3e3,ad7fd6825ab08286 X-Google-Attributes: gidfa3e3,public From: Richard Wilkman <rwilkman@inprise.com> Subject: Re: Inspecting variables in Java/AWT code Date: 1998/07/02 Message-ID: <359BA634.24E932AD@inprise.com> X-Deja-AN: 368106258 Content-Transfer-Encoding: 7bit References: <35773EF2.6005@industech.com> <359AD644.F7E2C0AC@inprise.com> Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.debugger,borland.public.jbuilder.ide