From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: igc statistics display
Date: Thu, 09 Jan 2025 11:12:10 +0100 [thread overview]
Message-ID: <m2jzb42t51.fsf@gmail.com> (raw)
In-Reply-To: <87frls9vxa.fsf@gmail.com> (Helmut Eller's message of "Thu, 09 Jan 2025 10:30:09 +0100")
Helmut Eller <eller.helmut@gmail.com> writes:
> On Thu, Jan 09 2025, Gerd Möllmann wrote:
>
>> I thought someone might have a similar use-case, and could give advice
>> what to use for something like that, preferably a small implementation
>> resistance, of course. Or, might be interesting helping, which would of
>> course be even better, because I'm a bit out of my comfort zone here.
>
> I'm currently learning a bit to use systemtap. It seems that systemtap
> is similar to dtrace, which I think is available for macOS. Maybe you
> could try that. Unfortunately, systemtap seems to be targeted more at
> kernel code than at user space code.
>
> I mostly follow the advice from here:
> https://www.brendangregg.com/blog/2015-07-08/choosing-a-linux-tracer.html
>
> Helmut
That's an interesting thought! Maybe one could generate perf events, or
what they are called. don't remember much about dtrace. And I would have
to check what macOS allows one to do without disabling security measures
which itself would require a reboot in recovery mode. Very interesting!
And one would of course need some nice interface for displaying events.
Thanks!
next prev parent reply other threads:[~2025-01-09 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 8:22 igc statistics display Gerd Möllmann
2025-01-09 8:34 ` Eli Zaretskii
2025-01-11 11:04 ` Matthias Meulien
2025-01-11 12:45 ` Gerd Möllmann
2025-01-09 9:30 ` Helmut Eller
2025-01-09 10:12 ` Gerd Möllmann [this message]
2025-01-10 6:26 ` Gerd Möllmann
2025-01-10 7:25 ` Eli Zaretskii
2025-01-10 7:31 ` Helmut Eller
2025-01-10 7:46 ` Eli Zaretskii
2025-01-10 8:05 ` Gerd Möllmann
2025-01-10 8:22 ` Eli Zaretskii
2025-01-10 9:02 ` Gerd Möllmann
2025-01-10 11:24 ` Eli Zaretskii
2025-01-10 8:23 ` Helmut Eller
2025-01-10 9:04 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2jzb42t51.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).