GNU bug report logs - #22114
24.5; [PATCH] Allow profiler.el to display reports after stopping

Previous Next

Full log

View this message in rfc822 format

From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
To: John Wiegley <jwiegley <at> gmail.com>
Cc: 22114 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping
Date: Tue, 8 Dec 2015 18:56:54 +0100

> I think the OP wants to:
> 
>   1. Start a profile
>   2. View the "results in progress"
>   3. Allow it to continue execution
>   4. View the "results at the end"

This would be a nice addition to have, but is currently not possible
(and not what I'm after with this patch).  The very act of viewing the
results in progress (which requires accessing the profiler log) creates
a log *and* resets the profiler.  If you access the log again while the
profiler is still running, you'll get a new log starting from that point
of time and spanning until access time.  This can be repeated ad nauseam
and is IMO rather unhelpful.

What can be fixed though is the behaviour of profiler report with a
stopped profiler.  You are still limited to accessing the profiler log
once, but if you make profiler.el cache it (be it by storing it in a
variable before stopping or by opening an already existing profiler
report buffer), the user won't be aware of this limitation, because no
matter how often they display the report, it will stay exactly the same
and not throw an error.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.