Bug 160987 – Profiler do not see classes from extension directories

HOME \ Community

Bug 160987 - Profiler do not see classes from extension directories

Summary:

Profiler do not see classes from extension directories

Status:	RESOLVED FIXED

Product:	profiler
Component:	Base
Version:	4.1
Platform:	All All

Priority:	P2 (vote)
Target Milestone:	6.7
Assigned To:	Tomas Hurka
QA Contact:	issues@profiler

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-24 10:06 by Tomas Hurka
Modified:	2009-03-25 09:28 (History)

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 From Tomas Hurka 2009-03-24 10:06:38

Handling of jars in extension directories (<java-home>/jre/lib/ext,
<java-home>/lib/ext) is broken. As a result profiler cannot profile classes
from  jars in 
extension directories if local profiling is selected and those classes are
loaded by system or bootstrap classloader.

------- Comment #1 From Tomas Hurka 2009-03-24 10:51:29 -------

Fixed in profiler-main
changeset:   123081:f315c65bfb22
user:        Tomas Hurka <thurka@netbeans.org>
date:        Tue Mar 24 10:49:07 2009 +0100
summary:     bugfix #160987, computation of path for extension jar fixed

------- Comment #2 From qa 2009-03-25 09:28:44 -------

Integrated into 'main-golden', will be available in build *200903250219* on
http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/f315c65bfb22
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #160987, computation of path for extension jar fixed