oprofile in pt-stalk won't work with galera/pxc

Bug #1152571 reported by Raghavendra D Prabhu on 2013-03-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT

Bug Description

This is how oprofile and its utils are invoked

      local mysqld_path=$(_which mysqld);
      if [ "$mysqld_path" -a -f "$mysqld_path" ]; then
         $CMD_OPREPORT \
            --demangle=smart \
            --symbols \
            --merge tgid \
            session:pt_collect_$p \
            "$mysqld_path" \
            > "$d/$p-opreport"


The galera library is dlopened by wsrep as a plugin. However, I
think, invoking opreport as above won't involve those.

Speaking of which, I don't think any other plugins (which are similarly dlopened) will feature either (plugins like the PAM etc.).

So, this needs to be fixed - either in how this is invoked or

I am not completely sure how can this be achieved in oprofile:

a) Different oprofile specification involving those libraries.

b) Separate global opcontrol report.

Other than this, I think perf should handle this perfectly, I
remember filing a bug for this but closed later as wishlist or

tags: added: pt-ioprofile pt-stalk pxc
Changed in percona-toolkit:
status: New → Confirmed

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1090

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers