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.
Summary: | Line numbers for PPs are shown incorrectly | ||
---|---|---|---|
Product: | profiler | Reporter: | Alexander Kouznetsov <mrkam> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | REOPENED --- | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Alexander Kouznetsov
2007-03-15 14:42:17 UTC
In fact this is partially the same problem as in Issue 97976 so marking as its duplicate. On the other side, line numbers will change in the Report even if profiling session is finished - actually header of the report just displays actual Profiling Point properties, not conditions for which the data have been obtained. *** This issue has been marked as a duplicate of 97976 *** This is not a duplicate since line numbers could change without modification of PPs - just one new line or line removal will cause numbers to be incorrect. However, lines are indeed updated when profiling is finished. Thus I'm lowering the priority. OK, not a duplicate, but see the explanation about report header - it's not related to conditions of collected data (note that the report can be shown even if no data are available). I would like to clarify what this issue is about: it is about the fact that when you click on line number in PP report you could see that opened line has different number. This is because real line numbers could be changed while report header is not synchronized according to these changes. It synchronizes only at profiling session start/stop. Even this is still issue I believe P4 is not a good topic at the moment. Next time please describe clearly enough what the real problem is so anyone other can also understand it. Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode. Target milestone cleanup. Milestone cleanup: future->next |