Closed Bug 673627 Opened 13 years ago Closed 13 years ago

--enable-callgrind should turn on --enable-profiling

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla8

People

(Reporter: sfink, Unassigned)

Details

(Whiteboard: [inbound])

Attachments

(1 file)

--enable-profiling means, as far as I can tell, "add commands to appropriate global objects that allow controlling profiling" (so start/stop/pause/resume/etc.) Many profiler-like things don't really need that sort of thing, but Callgrind must be explicitly started (AFAICT; I haven't actually used it). So it makes little sense to use --enable-callgrind without --enable-profiling. Other profiling options already enable --enable-profiling, too, so this isn't a first. (nb: I made this patch to work around another problem which I have correctly resolved in other ways, so if there's some reason to not do this, then it's not going to break anything. For example, if we decide to --enable-callgrind by default, it would widen the attack surface very slightly to also --enable-profiling.)
Attachment #547856 - Flags: review?(dmandelin)
Comment on attachment 547856 [details] [diff] [review] --enable-callgrind turns on --enable-profiling Review of attachment 547856 [details] [diff] [review]: -----------------------------------------------------------------
Attachment #547856 - Flags: review?(dmandelin) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla8
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: