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.

Bug 67125 - No profiling results available for Code Fragment profiling if the main method is selected as the code fragment
Summary: No profiling results available for Code Fragment profiling if the main method...
Status: CLOSED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-19 14:28 UTC by iformanek
Modified: 2007-02-20 18:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-10-19 14:28:04 UTC 
No profiling results available for Code Fragment profiling if the main method 
is selected as the code fragment. The app this occured on just called bunch of 
static methods to compute something. When it finished, the message was just 
about closing the VM, the user was not prompted to take snapshot of results - 
although the whole code fragment was indeed executed.
Comment 1 iformanek 2005-10-20 16:41:12 UTC 
Jirko, please take a look at this for M11
Comment 2 Jiri Sedlacek 2005-11-16 12:48:39 UTC 
Tested on simple app with just few static methods (see below), works fine - 
asks to take snapshot. Do you still have that app?


Testing app:

    public static void writeSomething() {
        System.err.println("Writing something...");
    }
    
    public static int computeSomething() {
        return 1 + 1;
    }
    
    public static int computeSomethingComplex(int number) {
        return computeSomething() * number;
    }
    
    public static String getDoneString() {
        return "Done...";
    }
    
    public static void main(String[] args) {
        writeSomething();
        System.err.println(computeSomething());
        System.err.println(computeSomethingComplex(2));
        System.err.println(getDoneString());
    }
Comment 3 iformanek 2005-11-28 13:21:23 UTC 
Does not seem to be reproducible.
Comment 4 ehucka 2006-10-09 12:09:33 UTC 
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-20 10:27:21 UTC 
Closing old issues
Comment 6 Alexander Kouznetsov 2007-02-20 18:10:37 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.