Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / First Aid / January 2007

Tip: Looking for answers? Try searching our database.

NetBeans 5.5 debugging, can't see values of local variables

Thread view: 
aleksfadeev@gmail.com - 04 Jan 2007 02:52 GMT
When I debug I can't see values of local variables, There is a message
though "Variable information is not available, source compiled without
-g options" But in the properties of the project
Build\Compiling\Additional Compiler Options I entered -g.  What do I do
wrong? How to make debugger see local variables?
Lew - 04 Jan 2007 05:14 GMT
> When I debug I can't see values of local variables, There is a message
> though "Variable information is not available, source compiled without
> -g options" But in the properties of the project
> Build\Compiling\Additional Compiler Options I entered -g.  What do I do
> wrong? How to make debugger see local variables?

If you look just above the "Additional Compiler Options" box in the "Project
Propeties" dialog, "Build/Compiling" option, you will note two checkboxes. The
first is labeled "Generate Debugging Info". The box labeled "Additional
Compiler Options" is for *additional* options, that means in addition to the
two specified by the checkboxes.

Personally, I always check both. Under Netbeans I never have a reason to run
without "-g" nor to use deprecated APIs. I almost never use the additional
options. I do have one long-running server process on which I specify
"-server", and I am experimenting in that project with various "-XX"
garbage-collection options.

- Lew
aleksfadeev@gmail.com - 04 Jan 2007 05:54 GMT
Thanks, it just didn't click in my mind that I need to check both check
boxes, thanks for the reply. I checked both boxes and it started
working, even without explicitly specifying -g option.
Lew - 04 Jan 2007 13:35 GMT
> Thanks, it just didn't click in my mind that I need to check both check
> boxes, thanks for the reply. I checked both boxes and it started
> working, even without explicitly specifying -g option.

If you only care about debugging, you do not need to check the "deprecated
APIs" choice. You only need the "debugging" checkbox.

My point about my use of the "deprecated APIs" choice is that I find that
useful in addition to debugging info. The two are independent.

- Lew
aleksfadeev@gmail.com - 05 Jan 2007 01:23 GMT
Apparently there is some misunderstanding from my side, it works with
one class but if I want to debug another one I still get the same
problem, both classes are in the same project and compiled with the
same options(I checked both boxes, and try to add/remove -g option
too).
PS: I am a .Net programmer so don't blame me too much, never thought
that debugging can be such a pain in my a.s.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.