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: Eli Zaretskii <eliz <at> gnu.org>
Cc: John Wiegley <jwiegley <at> gmail.com>, 22114 <at> debbugs.gnu.org
Subject: bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping
Date: Thu, 10 Dec 2015 10:18:04 +0100

> This is a completely different issue, and AFAIU the proposed patch
> didn't allow that.  The C-level implementation of producing a profiler
> log (which is then used to format a report) resets the profile data
> once it returns the log, and then starts collecting the profile data
> anew.  The OP's patch didn't change that.

How feasible would it be to make the log a regular hash table, fill it
with vectors of the right size and then manipulate these vectors every
time a profiling signal is received?  Or alternatively, fiddle with the
hash table values?  A successful patch doing that would remove the need
for being clever about storing logs/reports, resetting logs and on top
of that allow you to view in-progress reports like John Wiegley
suggested.

Previous Next

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