[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Elisp native profiler
From: |
Paul Eggert |
Subject: |
Re: Elisp native profiler |
Date: |
Tue, 25 Sep 2012 12:21:39 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 |
On 09/25/2012 10:28 AM, Stefan Monnier wrote:
> while it runs non-trivial code, it doesn't make any
> system-call or anything like that
But there are races if the SIGPROF handler runs in
some other thread, no? That bug could be worked around
by using thread-specific timers (which are available
in recent GNU/Linux but not older versions or in other
POSIXish platforms). More portably, albeit more slowly,
the SIGPROF handler could use deliver_process_signal,
like the other handlers of process signals.
A lesser question: why does the profiler use SA_SIGINFO?
It doesn't seem to use the extra info that SA_SIGINFO delivers.
- Elisp native profiler, Stefan Monnier, 2012/09/24
- Re: Elisp native profiler, Juanma Barranquero, 2012/09/25
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/25
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/25
- Re: Elisp native profiler, Stefan Monnier, 2012/09/25
- Re: Elisp native profiler,
Paul Eggert <=
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/25
- Re: Elisp native profiler, Stefan Monnier, 2012/09/25
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/27
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/27
- Re: Elisp native profiler, Stefan Monnier, 2012/09/27