Over the last few weeks the debug team has been going through the dreaded and controversial "Resolved - Later" bugs and feature requests. I wasn't able to come up with the right Bugzilla query to get exact statistics, but I know we had over 800 Resolved-Later bugs last month, and now we're sitting at 715. Not bad - that's over a 12% reduction! Some bugs had been fixed along the way (always a nice surprise), some had become irrelevant, some were re-opened to be addressed, and some were even re-opened with fresh patches to be applied soon.
Just another seven months and we'll have had a chance to look at each one :-) Be patient.
How about this one: https://bugs.eclipse.org/bugs/show_bug.cgi?id=40912
ReplyDelete(Viewing method return values in the JDT Debugger).
I think that it may have fallen down a bit of a hole because it's logged against platform and marked as "Resolved - Later". It's been raised a few times against the JDT but those have been closed as duplicates. As far as I can see the necessary stuff is there in the JDK to support it so it could be fixed now.
If anyone can give me any pointers on where to start I could have a go at submitting a patch. I know that it's something that bugs me quite often when debugging - I can't be the only one can I?
Java 6 has supplied the required information in a round about way - on method exit events. The problem is that we don't use method exit events for stepping... so meshing the two together will be a bit messy. I updated the bug with a comment... but it's really just a starting point.
ReplyDeleteWow - that was a quick response, thanks.
ReplyDelete(and thanks for your work making the JDT debugger so great in the first place too!).ft