From: "Frank Ch. Eigler" <fche@redhat.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: systemtap@sourceware.org
Subject: Re: SDTs with data types and argument names
Date: Mon, 13 Jan 2020 20:54:00 -0000 [thread overview]
Message-ID: <20200113205406.GE6118@redhat.com> (raw)
In-Reply-To: <CAMsr+YHGqQFQPqLsiTCpHv42PVA0UC+J_HCFsB4vp6c_QKD8ew@mail.gmail.com>
Hi -
> > Yeah. I believe there was a kernel-bpf-oriented group last year, who
> > were speculating extending sdt.h in a similarly motivated way.
>
> Good to know. Any idea who may've been involved? It'd be good to
> collaborate and not duplicate work or explore a dead-end already followed.
https://web.archive.org/web/20190528152614/http://vger.kernel.org/lpc-bpf2018.html#session-11
"enhancing user defined tracepoints"
(h/t serhei) (btw, where did vger itself go??? did it merge with
Decker and disappeared into another dimension?)
> Indeed. And the latter option is hairy for complex and portable software:
> you must get exactly the right header version, but you must also ensure you
> have any number of preprocessor macros etc set precisely the same. There
> can be header inclusion order considerations and more. I'm very reluctant
> to use the automated header processing features.
Those provisos are all valid, yet it turns out to be useful & capable
a lot of the time. If there is a "-devel" level packaged set of
headers, they should be well enough engineered to let this work.
> [...] I don't know of any way to ask gcc/gdb/binutils/etc to retain
> a subset of debuginfo in an executable when it's being stripped, and
> I doubt that'd be popular or accepted anyway. [...]
See "BTF" and "CTF" for two efforts to keep some wee subsets of
debuginfo on the installation medium. And see
debuginfod.systemtap.org :-) for a distribution vehicle for full
mainstream debuginfo.
- FChE
next prev parent reply other threads:[~2020-01-13 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 3:00 Craig Ringer
2019-12-20 4:13 ` Craig Ringer
2020-01-09 18:46 ` Frank Ch. Eigler
2020-01-13 5:28 ` Craig Ringer
2020-01-13 20:54 ` Frank Ch. Eigler [this message]
2020-01-13 21:08 ` Frank Ch. Eigler
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=20200113205406.GE6118@redhat.com \
--to=fche@redhat.com \
--cc=craig@2ndquadrant.com \
--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).