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 12798 - No class loader for classes being debugged when a working directory has been set.
Summary: No class loader for classes being debugged when a working directory has been ...
Status: CLOSED WORKSFORME
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-13 02:34 UTC by isullivan
Modified: 2001-07-27 09:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description isullivan 2001-06-13 02:34:49 UTC
This happens in build 39.
Using the following class I get null for the Class Loader after I set a working 
directory (in the Debugger Execution). Without a working directory I get 
sun.misc.Launcher$AppClassLoader@12c2dc8
This is a problem for me since external jar's don't seem to get loaded properly 
when there is no class loader for the main class. This only happens in the 
debugger, when doing Execute there seems to be a class loader.

package testbed;

public class Tester extends java.lang.Object {
    public Tester() {
    }

    public void test(){
        System.out.println(getClass());
        System.out.println(getClass().getClassLoader());
    }
    
    public static void main (String args[]) {
        Tester t = new Tester();
        t.test();
    }
}
Comment 1 Jan Stola 2001-07-26 15:11:40 UTC
I am sorry. I cannot reproduce this issue.
The line in question correctly returned
class loader in all my attempts.
I do not understand what can cause
such behaviour. I can hardly belive
that this issue was caused by the debugger
module. It seems to be issue of the JDK.
What JDK do you use?
Comment 2 isullivan 2001-07-26 20:06:41 UTC
This happened to me in both JDK 1.3 and JDK 1.3.1.
It also happened in Netbeans 3.1 as well as 3.2....I guess there 
could be something wrong with my install, but it's wierd that it 
happened in the fresh install of NB 3.2 and JDK 1.3.1 
Comment 3 Jan Stola 2001-07-27 09:22:05 UTC
Resolution Worksforme -> Status Closed.