all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: igc statistics display
Date: Fri, 10 Jan 2025 09:23:37 +0100	[thread overview]
Message-ID: <87o70f84c6.fsf@gmail.com> (raw)
In-Reply-To: <m2msfzxfet.fsf@gmail.com> ("Gerd Möllmann"'s message of "Fri, 10 Jan 2025 09:05:14 +0100")

On Fri, Jan 10 2025, Gerd Möllmann wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>> SystemTap is not the ideal means for such a facility.  Its only
>> significant advantage is that it's supported by GDB.  But its huge
>> disadvantage is that it's a Linux-only facility.

I think drrace is also available for Windows.

>> In addition, I feel that this is too low-level for our purposes.  We
>> need something more akin to trace-redisplay.
>
> I must say upfront that I've only read about dtrace for a couple hours
> and asked Gemini a few questions. From that, my understanding is that an
> application can generate its own application-specific events that carry
> additional data, including strings, int, floats, and so on, structs (not
> sure if I believe Gemini in that case, but who knows). (Helmut, please
> correct me if that's wrong.)

Applications can define "static trace points".  In practice, that means
the application has macro calls like DTRACE_PROBE(name, arg1, arg2..)
in the source code at interesting places.  Obviously, the same macro
could be configured to work with dtrace or systemtap or something else.

An advantage of tools like dtrace and systemtap is that they can patch
code: static trace points are nop instructions, until activated.  So
very cheap, if not used.  Ironically, that's almost impossible to do by
the application itself.

Static trace points are useful, but with dtrace/systemtap it's also
possible to set trace points by line number, as in gdb.

Helmut



  parent reply	other threads:[~2025-01-10  8:23 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o70f84c6.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.