Closed
Bug 111024
Opened 24 years ago
Closed 22 years ago
Changes in NSPR to allow for profiling with Chronoscope
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: sfraser_bugs, Assigned: sfraser_bugs)
Details
Attachments
(1 file, 2 obsolete files)
13.28 KB,
patch
|
Details | Diff | Splinter Review |
This bug is a placeholder for some patches to allow for profiling Mozilla with
Chronoscope.
Assignee | ||
Comment 1•24 years ago
|
||
Only apply this patch if you need to do profiling. It's not for general
consumption.
Comment 2•24 years ago
|
||
Chronometer? I thought it was Chronoscope?
Assignee | ||
Comment 3•24 years ago
|
||
The patch is old -- the name changed because a 'chronometer' project already
existed on SourceForge.
Assignee | ||
Comment 4•24 years ago
|
||
This patch contains changes to make profiling with Chronoscope better. The
changes in xpfe/bootstrap/nsApprunner.cpp are experimental; you'll want to
mess with those depending on what you need to profile.
Assignee | ||
Updated•24 years ago
|
Attachment #58569 -
Attachment is obsolete: true
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 5•24 years ago
|
||
Comment on attachment 62228 [details] [diff] [review]
Tree-wide patch for Chronoscope profiling
Simon, my understanding is that you are
not planning to check this patch in.
Those who want to use Chronoscope are expected to
manually apply this patch to their source tree.
Correct?
Assignee | ||
Comment 6•24 years ago
|
||
Exactly. What should tbe bug status be for this? Later? Remind?
Comment 7•24 years ago
|
||
Maybe WONTFIX? :-)
Assignee | ||
Comment 8•23 years ago
|
||
Attachment #62228 -
Attachment is obsolete: true
Comment 9•22 years ago
|
||
Marked the bug WONTFIX. The purpose of this bug is
to archive a patch that people can apply to profile
Mozilla with Chronoscope. We do not intend to check
in the patch.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•