This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 91214 [details] screenshot of debugger panel showing missing values for objects the debugging variables pane does not show the object type in the Value column. see the attached screen shot. There is a discussion in the forum about this here: http://forums.netbeans.org/viewtopic.php?p=54665
who decides the priority on these issues? any way to get this bumped up to a P1? it would seem kind of a glaring feature to be missing, at least in my world. Issue still exists in 6.9M1, have not tried the nightly similar to 163637 and 177039
(In reply to comment #1) > who decides the priority on these issues? any way to get this bumped up to a > P1? No way, sorry. See http://wiki.netbeans.org/BugPriorityGuidelines > it would seem kind of a glaring feature to be missing, at least in my > world. Issue still exists in 6.9M1, have not tried the nightly > > similar to 163637 and 177039 I believe you. Actually, at the time being, I am not sure this is defect or enhancement. But, keep it as it is for now. Your QA ;).
I've tried 6.8 and the latest nightly build and the variable list just shows 'object' for the type. The issue was originally reported for XP, I'm running Win7 so maybe that makes a difference. Anyway, still this isn't very useful. It should show the object class.
(In reply to comment #3) > I've tried 6.8 and the latest nightly build and the variable list just shows > 'object' for the type. The issue was originally reported for XP, I'm running > Win7 so maybe that makes a difference. > > Anyway, still this isn't very useful. It should show the object class. this is not platform related issue.
The showing of object class is very important for software evaluation/study, but also for debugging of OO PHP code! The class name of the class the object was generated with is meant - please dont confuse with implementation class name, where the called method/variable is implemented (can be a super class or so)! In OO PHP there is no "object" type, just as there is no "primitive" type (its a pointer type on interpreter tier). The type of object variable is always the classname with that the object was created! otherwise the debugger variables view is not really suitable for OO development (tracing/debugging)! i have 1000 classes and all are of type "object"? sorry, but not acceptable! :) And there is no workaround, therefore P1! i refer to ZendStudio implementation of Variables view! Furthermore, thats copyable - i can copy the content of the view, paste it to excel/openoffice calc and print it out for study! And please please please!... Its a big decision criterion for use NetBeans instead of ZendStudio sorry for my bad english best regards
Canditate for 6.9.1
@nadobnykh - no need for all the !!, comes across as kind of abusive in a CAPS like way. Looking at the history shows that the issue was marked for fix in the next milestone release on the 20th of this month so the developers are aware of the issues and it is slated to be resolved. Also look at the comments noted in this issue as to how issues are prioritized before 'demanding' a P1 status. Play nice in the sandbox
http://hg.netbeans.org/web-main/rev/dfd90d3cfbb5
fix has been verified in build 2010-05-31_15-03-59. Please, transplant into 69FCS after RC2 is out (current status for RC2 is NoGo due to fx composer issues). thanks.
http://hg.netbeans.org/release69/rev/e275963df127
Integrated into 'main-golden', will be available in build *201006030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/dfd90d3cfbb5 User: Radek Matous <rmatous@netbeans.org> Log: #177039 - Debugger - variables pane does not show object type
verified in release69 clone Product Version: NetBeans IDE 6.9 (Build 100609-a94d6a4a87fe) Java: 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01
Transplanted to release691 as 90d056757956
Added keyword 6.9.1_CANDIDATE to bugfixes, which were integrated in release69 repository *after* the release691 clone has been created.
Verified that the fix is available in the release691 repository.
*** Bug 183885 has been marked as a duplicate of this bug. ***