[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dtrace
From: |
Gerd Möllmann |
Subject: |
Re: dtrace |
Date: |
Tue, 14 Jan 2025 14:41:37 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: Emacs Devel <emacs-devel@gnu.org>, Helmut Eller
>> <eller.helmut@gmail.com>, Pip Cet <pipcet@protonmail.com>, Nix
>> <nix@esperi.org.uk>, Arsen Arsenović <arsen@gentoo.org>
>> Date: Tue, 14 Jan 2025 08:39:35 +0100
>>
>> Sam James <sam@gentoo.org> writes:
>>
>> > Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> >
>> >> Please find attached the beginnings of DTrace support. The diff is
>> >> based on my Emacs but probably applies to scratch/igc as well.
>> >
>> > Oh, this sounds exciting!
>> >
>> >> [...]
>> >
>> >> [2. text/x-patch; dtrace.diff]...
>> >
>> > This looks empty over here.
>>
>> Sorry for that. Hope this one works:
>
> Thanks. Can you tell in a few words what does this patch provide for
> Emacs?
If makes Emacs a dtrace USDT (= Userland Statically Defined Trace)
provider, like Python.
https://docs.python.org/3/howto/instrumentation.html
With this, a developer can define probes that can be used for all sorts
of things in the C code. The sky is the limit. There is currently only 1
test probe in igc.c to see if the build works.
- dtrace, Gerd Möllmann, 2025/01/14
Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Helmut Eller, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Eli Zaretskii, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Eli Zaretskii, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16