opjitconv is not installed, breaking oprofiling of Python Unladen Swallow JIT (or anything else that uses LLVM JIT)

Bug #525932 reported by Elliot Murphy on 2010-02-22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
oprofile (Ubuntu)

Bug Description

Binary package hint: oprofile

Working on http://code.google.com/p/unladen-swallow/ at PyCon 2010, I discovered that oprofile does not work for samples emitted by the LLVM JIT (they show up as anonymous rather than being linked to the python source, line and name).

The problem is that the oprofile package was not installing the opjitconv binary which is needed for opreport to be able to create useful reports on the JIT samples.

I have built an tested a package which does install opjitconv, and this enables profiling to work as expected. I will propose a branch for this now, and would like to also push this fix back into Karmic as it should be very low risk and the missing binary makes it very hard for anyone wanting to do profiling to speed up python.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oprofile - 0.9.4+cvs20090629-2.1ubuntu4

oprofile (0.9.4+cvs20090629-2.1ubuntu4) lucid; urgency=low

  * debian/rules (LP: #525932)
    - Need opjitconv installed to enable JIT profiling of unladen swallow.
 -- Elliot Murphy <email address hidden> Mon, 22 Feb 2010 12:36:20 -0500

Changed in oprofile (Ubuntu):
status: New → Fix Released
Revision history for this message
Elliot Murphy (statik) wrote :

The last upload fixed a major part of the problem, but overlooked that an oprofile system user needed to be created. If the user does not exist, then JIT profiling silently fails. see README_PACKAGERS in the oprofile source distribution for more info. Pushed up a second branch for review which takes care of adding the user, and confirmed that JIT profiling now works fine with this version of the package.

Changed in oprofile (Ubuntu):
status: Fix Released → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oprofile - 0.9.6-1ubuntu1

oprofile (0.9.6-1ubuntu1) lucid; urgency=low

  [ Matthias Klose ]
  * Merge with Debian (no remaining changes). LP: #495140.
  * Split out libopagent1 runtime library.

  [ Elliot Murphy ]
  * debian/oprofile.postinst (LP: #525932)
    - Really really make it work this time by adding the
      oprofile:oprofile system user and group as required
      for JIT support (see README_PACKAGERS)

  [ Steffen Neumann ]
  * Add documentation about vmlinux / linux-image-debug.ddeb. LP: #497424.

oprofile (0.9.6-1) unstable; urgency=low

  * New upstream release

oprofile (0.9.5-1) unstable; urgency=low

  * Add myself as Uploader, thanks to LIU Qi for accepting me as co-maintainer
  * New upstream release (Closes: #496146)
  * Remove README.Debian, which was outdated
  * Update to Standards-Version 3.8.3 (no changes)
  * Add myself to debian/copyright
  * Add doc-base registration
  * Use quilt to manage changes to upstream sources
  * Make oprofile be able to start in timer mode, thanks to Joachim
    Berdal Haga for the patch (Closes: #548574)
  * Do not remove JIT profiling support (Closes: #543681)
  * Support for DEB_BUILD_OPTIONS=noopt (Closes: #429157)
 -- Matthias Klose <email address hidden> Fri, 26 Feb 2010 08:47:38 +0100

Changed in oprofile (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers