From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: alex.branham@gmail.com, 34235@debbugs.gnu.org
Subject: bug#34235: 27.0.50; lisp profiler does not work
Date: Wed, 30 Jan 2019 17:48:26 +0200 [thread overview]
Message-ID: <83womm1705.fsf@gnu.org> (raw)
In-Reply-To: <20190130133311.GA5463@ACM> (message from Alan Mackenzie on Wed, 30 Jan 2019 13:33:11 +0000)
> Date: Wed, 30 Jan 2019 13:33:11 +0000
> Cc: 34235@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> For what it's worth, I see the bug in master in GNU/Linux, starting off
> with emacs -Q, visiting xdisp.c, M-x profiler-start <CR> <CR>, M->, M-x
> profiler-report.
>
> I see in the report just the single entry for Automatic GC, like Alex.
Thanks, I hope you (or someone else who sees this) will be able to
debug this.
next prev parent reply other threads:[~2019-01-30 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 18:34 bug#34235: 27.0.50; lisp profiler does not work Alex Branham
2019-01-29 16:06 ` Eli Zaretskii
2019-01-30 13:33 ` Alan Mackenzie
2019-01-30 15:40 ` Alex Branham
2019-01-30 16:15 ` Alan Mackenzie
2019-01-30 16:23 ` Alex Branham
2019-01-30 16:43 ` Eli Zaretskii
2019-01-30 20:47 ` Alex Branham
2019-01-30 16:41 ` Eli Zaretskii
2019-01-30 15:48 ` Eli Zaretskii [this message]
2019-02-01 21:47 ` bug#34235: 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix division by zero bug). Problems with glibc Alan Mackenzie
2019-02-01 22:04 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.21.1902012301310.8200@nanos.tec.linutronix.de>
2019-02-02 10:44 ` Alan Mackenzie
[not found] ` <20190202104404.GA1067@ACM>
2019-02-04 17:25 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.21.1902041724200.3006@nanos.tec.linutronix.de>
2019-02-05 13:54 ` Alan Mackenzie
2019-02-02 2:07 ` bug#34235: 0e334db6bb4b1fd1e2d72c1f3d8f004313cd9f94 (posix-timers: Fix, " Paul Eggert
2019-02-02 9:21 ` Thomas Gleixner
2019-02-02 14:02 ` Alex Branham
[not found] ` <alpine.DEB.2.21.1902021020020.8200@nanos.tec.linutronix.de>
2019-02-03 6:28 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83womm1705.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34235@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=alex.branham@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.