From: Alan Mackenzie <acm@muc.de>
To: Alex Branham <alex.branham@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 34235@debbugs.gnu.org
Subject: bug#34235: 27.0.50; lisp profiler does not work
Date: Wed, 30 Jan 2019 16:15:21 +0000 [thread overview]
Message-ID: <20190130161521.GA4051@ACM> (raw)
In-Reply-To: <874l9qjgrx.fsf@gmail.com>
Hello, Alex and Eli.
On Wed, Jan 30, 2019 at 09:40:02 -0600, Alex Branham wrote:
> On Wed 30 Jan 2019 at 07:33, Alan Mackenzie <acm@muc.de> wrote:
> > 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.
> > I last updated my repository yesterday, just before midday UTC.
> Thanks, Alan. Good to know it's not just me.
> Since submitting this bug, I've discovered that it affects previous
> versions of Emacs as well. Emacs from git master that I compile myself,
> Emacs 26.1 from my distro (nixOS), and Emacs 25.3 from my distro. I
> haven't had time yet to dig in much more than that, but figured I'd
> report that as well since it rules out the pdumper.
It seems to be a Linux problem, at least at my end.
I see the bug with kernel versions 4.19.17 and 4.19.13.
I don't see the bug with versions 4.18.19 and 4.19.10.
It seems some incompatibility between Emacs and Linux was introduced in
one of the kernels 4.19.1[123].
I don't know how to debug this any further.
> Alex
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-01-30 16:15 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190130161521.GA4051@ACM \
--to=acm@muc.de \
--cc=34235@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).