GNU bug report logs - #72559
31.0.50; profiler-report-write-profile produced unreadable data

Previous Next

Package: emacs;

Reported by: Ihor Radchenko <yantar92 <at> posteo.net>

Date: Sat, 10 Aug 2024 12:42:01 UTC

Severity: normal

Found in version 31.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 72559 <at> debbugs.gnu.org
Subject: bug#72559: 31.0.50; profiler-report-write-profile produced unreadable data
Date: Sat, 10 Aug 2024 15:50:24 +0300
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Date: Sat, 10 Aug 2024 12:41:52 +0000
> 
> Since ~few months ago, I started having issues with profiler dumps
> shared by users.  The latest example is in
> https://list.orgmode.org/87r0axvu7y.fsf <at> gmail.com/T/#u
> 
> When trying to open the profiler data with M-x profiler-find-profile, I
> keep getting
> profiler-find-profile: Invalid read syntax: "#<", 2, 64028
> or similar errors.
> 
> In other words, unreadable objects are somehow dumped, rendering the
> profiles useless.

Does this happen on the emacs-30 branch as well?

In any case, bisection would be useful.

Thanks.




This bug report was last modified 336 days ago.

Previous Next


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