From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/29676] New: wildcard function/symbol expansion inconsistent in debuginfo vs nondebuginfo cases
Date: Wed, 12 Oct 2022 18:12:07 +0000 [thread overview]
Message-ID: <bug-29676-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29676
Bug ID: 29676
Summary: wildcard function/symbol expansion inconsistent in
debuginfo vs nondebuginfo cases
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
Binaries sometimes contain symbol tables or minidebuginfo that systemtap can
resolve process probes within:
stap -L 'process("/lib64/libc.so.6").function("__memset*")'
which match a bunch of assembler ifunc alternative functions by symbol name.
Unfortunately, if dwarf for this package is also available, then stap will
apparently only process the dwarf symbols, and not the minidebuginfo stuff,
so the same wildcard will produce an apprx. empty match list.
We should use the union of the two data sources if possible.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-10-12 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:12 fche at redhat dot com [this message]
2022-10-19 14:01 ` [Bug translator/29676] " rgoldber at redhat dot com
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=bug-29676-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).