public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29818] STAP probe map_failed is no longer generated.
Date: Wed, 30 Nov 2022 12:02:19 +0000 [thread overview]
Message-ID: <bug-29818-131-Z2V93tlgMy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29818-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29818
--- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Frank Ch. Eigler from comment #3)
> Interesting!
>
> To Pedro's question, enumerating probes in a compiled libc is a matter of a
> perf or readelf or stap command, not a problem. Such a thing could be a
> test case that matches the manual/probes.texi list against what turns out to
> be compiled.
>
> Consumers such as gdb should not assume/assert the existence of any
> particular probe, if at all possible.
We have a internal script (scripts/glibcelf.py) which has ELF parse support to
check against the elf/elf.h header definition, it should be feasible to extend
it support stapsdt notes and compare against the ones described in
manual/probes.texi (which could be obtained with another script).
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-11-30 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:29 [Bug dynamic-link/29818] New: " aburgess at redhat dot com
2022-11-22 12:30 ` [Bug dynamic-link/29818] " aburgess at redhat dot com
2022-11-22 15:11 ` simon.marchi at polymtl dot ca
2022-11-22 15:12 ` lsix at lancelotsix dot com
2022-11-23 14:06 ` adhemerval.zanella at linaro dot org
2022-11-28 15:35 ` pedro at palves dot net
2022-11-28 17:56 ` fche at redhat dot com
2022-11-30 12:02 ` adhemerval.zanella at linaro dot org [this message]
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-29818-131-Z2V93tlgMy@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).