opcontrol --vmlinux will only create KERNEL_RANGE but not update it
Bug #125647 reported by
James Troup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oprofile (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
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?
Revision history for this message
| Jeff Anderson (jander99) wrote | #1 |
| Changed in oprofile (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| rusivi2 (rusivi2-deactivatedaccount) wrote | #2 |
Revision history for this message
| James Troup (elmo) wrote | #3 |
| 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.
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.