Article View: borland.public.jbuilder.debugger
Article #5208Re: jdk 1.1.7 debugging?
From: Richard Wilkman
Date: Fri, 02 Oct 1998 00:00
Date: Fri, 02 Oct 1998 00:00
60 lines
3116 bytes
3116 bytes
Tad: The UI designer will use the classes from a new JDK -- live instances are runtime. The only item will be the degbugger and that will be solved with the 1.2 debug API for all JDK drops that support it. For those who like to split hairs, that means that any developer who does not move to the 1.2 JDK family will not see debug enhancements as Javasoft is not likely to backport the API (don't think it can even be done) to 1.1.8 or whatever follows 1.1.7. -Rich Tad Frysinger wrote: > > In article <361415CE.E74EAAE0@ici.net>, ejs@ici.net says... > > Okay I just installed JDK 1.1.7. Was easy to set up Jbuilder to use it > > and it runs great. > > But now when I try to debug I get the message "Unsupported debugging > > JDK." > > Please tell me that I have just forget to configure some silly option > > somewhere and this > > does not really mean that Jbuilder 2 can't debug 1.1.7 either. > > > > > Upon further thought - I know what the deal is. > > Currently, there is no concrete debugging API for Java that allows VM's > to be plugged in/out for debugging purposes. As such, the only way that > JBuilder can debug is to use the VM that runs the JBuilder product > itself. This means that you can only use the debugger for the JDK that > ships with JBuilder. Period. > > When Java supports a true debugging API that will allow products like > JBuilder to write to standard interfaces instead of specific JDK's, then > switching a JDK in (that also supports that interface) will also mean > using that same JDK for debugging (or powering the JBuilder visual > designer, for that matter). > > So the text on the box that everyone keeps pointing to should really be > read as: "Use JDK switching for runtime support against any JDK". You > can not use JDK switching for debugging support, visual designer support, > or any other support inherent in the JBuilder IDE itself. > > Tad Frysinger > [TeamB] -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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:
<3614F84A.3FAEA2DF@inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<361415CE.E74EAAE0@ici.net> <MPG.107e902dcbca0dea98991d@forums.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5c5,11ad4ee118bd4d40 X-Google-Attributes: gidff5c5,public X-Google-Thread: fa3e3,11ad4ee118bd4d40 X-Google-Attributes: gidfa3e3,public From: Richard Wilkman <rwilkman@inprise.com> Subject: Re: jdk 1.1.7 debugging? Date: 1998/10/02 Message-ID: <3614F84A.3FAEA2DF@inprise.com> X-Deja-AN: 397076751 Content-Transfer-Encoding: 7bit References: <361415CE.E74EAAE0@ici.net> <MPG.107e902dcbca0dea98991d@forums.borland.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