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.
Code run fine without the profiler but when trying to run it with the profiler ClassLoader.loadLibrary0 can't find external library.
Can you please submit more information? We would need at least messages.log or the whole error message and also information about build/jdk you are using.
This is the error stack init: profile-init: deps-jar: compile: profile: Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds (Protocol version: 8) Profiler Agent: Established local connection with the tool java.lang.UnsatisfiedLinkError: D:\VTK 5.05\VTKBin\bin\vtkRenderingJava.dll: Can't find dependent libraries at java.lang.ClassLoader$NativeLibrary.load(Native Method) Profiler Agent: Connection with agent closed at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751) Profiler Agent: Connection with agent closed at java.lang.ClassLoader.loadLibrary(C at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1647) at java.lang.Runtime.load0(Runtime.java:770) at java.lang.System.load(System.java:1005) at papermaterials.Main.<clinit>(Main.java:36) Profiler Agent: Initializing... Profiler Agent: Options: >D:\Program Files\NetBeans 6.5\profiler3\lib,5140,10< Profiler Agent: Initialized succesfully Exception in thread "main" Exception in thread "main" Java Result: 1 BUILD SUCCESSFUL (total time: 2 seconds) Config is: Product Version: NetBeans IDE 6.5 (Build 200811100001) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 System: Windows XP version 5.1 running on x86; Cp1252; en_AU (nb) Code runs when launched normally and in debug mode. But the profiler is not happy with it. Loaded the lib with both System.load (specifying the full path) as well as System.loadlibrary but I get the same problem.
Can you please attach the messages log file - from the output we can only see that some exception occurred, but not the stacktrace...
missing additional information for a few months -> resolving invalid Reporter: if it is still reproducible, please attach the message.log file and reopen. Thanks