From: Craig Ringer <craig@2ndquadrant.com>
To: systemtap@sourceware.org
Subject: Re: Code maintenance / verbosity: macros, enums, and casts
Date: Thu, 23 Jul 2020 13:16:12 +0800 [thread overview]
Message-ID: <CAMsr+YGGzFknAOyKf36r+63B=-MZsqJS2Aw9znyWaAFwToOK=Q@mail.gmail.com> (raw)
In-Reply-To: <CAMsr+YF-1-CXggj9KXjKRphDk2RqP9hNqMSwusk4Y2O50MXNQw@mail.gmail.com>
Replying-to-self with some notes/progress on this.
While I'm at it, having started to read more of the systemtap code
properly, it's an absolutely miraculous tool in terms of how easily the
complexity it deals with is hidden from the user. Truly incredible,
thankyou!
TL;DR: WIP patch at https://github.com/ringerc/systemtap-patches . Some
compile issues remain, so it's not even a PoC yet, but I think I've figured
out how it all has to work.
It didn't help that libdw itself, is not exactly ... documented. For anyone
else looking for documention on libdw, elfutils etc, this is one of the few
sources I found:
https://developer.ibm.com/technologies/systems/articles/au-dwarf-debug-format/
(Now that I think I worked much of it out, at some stage I hope I'll be
able to come and add a few comments in relevant places to help explain what
the various visitors do, how the dwarf_query stuff works and which ones
relate to which stap code constructs, etc.)
<https://developer.ibm.com/technologies/systems/articles/au-dwarf-debug-format/>
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise
prev parent reply other threads:[~2020-07-23 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 2:54 Craig Ringer
2020-07-21 4:11 ` Arkady
2020-07-23 5:16 ` Craig Ringer [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='CAMsr+YGGzFknAOyKf36r+63B=-MZsqJS2Aw9znyWaAFwToOK=Q@mail.gmail.com' \
--to=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).