public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@kenel.org>
Subject: perf probe: adding probe on C++ member/namespace function or versioned symbols
Date: Wed, 08 Dec 2021 21:08:13 +0100	[thread overview]
Message-ID: <2119579.vFYbnVOWES@milian-workstation> (raw)

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Hey there,

how can one escape function names for `perf probe`? It seems like the current 
parser is confused by the `:` which is common in C++ symbol names.

```
$ perf probe -F --exec /usr/lib/libQt5Widgets.so | grep syncBacking
QWidgetPrivate::syncBackingStore
QWidgetPrivate::syncBackingStore

$ perf probe --exec /usr/lib/libQt5Widgets.so --add 
QWidgetPrivate::syncBackingStore
Semantic error :There is non-digit char in line number.
...
```

Additionally, it is also not possible to pass a versioned symbol either:
```
$ nm -aD /usr/lib/libQt5Widgets.so | grep syncBacking
0000000000197480 T 
_ZN14QWidgetPrivate16syncBackingStoreERK7QRegion@@Qt_5_PRIVATE_API
00000000001973b0 T _ZN14QWidgetPrivate16syncBackingStoreEv@@Qt_5_PRIVATE_API
Semantic error :SRC@SRC is not allowed.
...
```

Is there a workaround available for this?

Thanks

-- 
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5272 bytes --]

             reply	other threads:[~2021-12-08 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 20:08 Milian Wolff [this message]
2021-12-09 10:47 ` perf probe: adding probe on C++ member/namespace function or versioned symbols James Clark
2021-12-15 13:10   ` Milian Wolff
2021-12-15 14:59     ` Arnaldo Carvalho de Melo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2119579.vFYbnVOWES@milian-workstation \
    --to=milian.wolff@kdab.com \
    --cc=acme@kenel.org \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox