opcontrol --vmlinux will only create KERNEL_RANGE but not update it

Bug #125647 reported by James Troup on 2007-07-12
Affects Status Importance Assigned to Milestone
oprofile (Ubuntu)

Bug Description

Binary package hint: oprofile

opcontrol --vmlinux will create KERNEL_RANGE if the variable is not yet set in daemonrc, but it will not update it. This means if you point opcontrol at a new kernel image that is on a different range to the one previously you start to silently lose kernel profiling data. There doesn't seem any sane reason not to recalculate the KERNEL_RANGE each time --vmlinux is used?

Jeff Anderson (jander99) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in oprofile (Ubuntu):
status: New → Incomplete

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

James Troup (elmo) wrote :

Looking at maverick's oprofile, the relevant code hasn't changed substantially since this was first reported.

Changed in oprofile (Ubuntu):
status: Incomplete → New
Changed in oprofile (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers