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 176571 - I/O usage Opened/Closed details are not shown if GNU tools and DTrace profiler are used
Summary: I/O usage Opened/Closed details are not shown if GNU tools and DTrace profile...
Status: RESOLVED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Profile (show other bugs)
Version: 6.x
Hardware: All All
: P2 normal (vote)
Assignee: Alexey Vladykin
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2009-11-11 10:14 UTC by Alexander Pepin
Modified: 2009-11-12 04:18 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 Alexander Pepin 2009-11-11 10:14:13 UTC 
See also Bug #176570
Steps to reproduce:
- add remote solaris host and set it as default using SmartSecureCopy and GNU
tool collection
- create Fractal sample
- set Extended DTrace profile configuration
- run the application
- when execution completes open I/O Usage table
- click on any file name
Result: "Opened at" "Closed at" details do not appear
It works fine if SS tools are used instead of GNU.
Comment 1 Alexey Vladykin 2009-11-12 01:52:01 UTC 
Will see what's going on
Comment 2 Alexey Vladykin 2009-11-12 02:40:45 UTC 
I can not reproduce this.

Are you sure you clicked on a real file, not <stdout>? For stdout there are no stacks available, it's OK.

Does waiting for several seconds help? The stacks have to go a longer road to the database than the I/O operations, so if the computer is very busy, I/O data can be already available, but not the stacks. Try waiting for several seconds and clicking on another file.

Did you see any exceptions in NetBeans log? An unexpected exception could theoretically interrupt the request for the stacks.

I need more information to understand and fix the problem.
Comment 3 Alexander Pepin 2009-11-12 04:18:30 UTC 
It works fine in the latest build.