From: Alex Branham <alex.branham@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 34235@debbugs.gnu.org
Subject: bug#34235: 27.0.50; lisp profiler does not work
Date: Wed, 30 Jan 2019 14:47:06 -0600 [thread overview]
Message-ID: <87pnsdzxdh.fsf@gmail.com> (raw)
In-Reply-To: <83lg3214g2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Wed 30 Jan 2019 at 10:43, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Alex Branham <alex.branham@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 34235@debbugs.gnu.org
>> Date: Wed, 30 Jan 2019 10:23:10 -0600
>>
>> > 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'm on kernel 4.14.95, so if it is a Linux issue, it's been backported.
>
> Do you keep records of your system updates? If so, can you look there
> for relevant recent updates, like glibc or some kernel modules/drivers
> or libraries?
nixOS keeps old systems laying around. I was able to go back to a system
that doesn't have this bug (back in December, nixos-version
18.09.1763.fbb7dbdb95d). The only differences in package versions
between this system and the next one (where the profiler doesn't work,
nixos-version 18.09.1829.0396345b794) is this:
- linux-4.14.89
+ linux-4.14.91
- python3-3.6.7
+ python3-3.6.8
- libjpeg-turbo-1.5.3
+ libjpeg-turbo-2.0.1
- cpupower-4.14.89
+ cpupower-4.14.91
If there's any other info I can share, let me know.
Thanks,
Alex
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-01-30 20:47 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 [this message]
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=87pnsdzxdh.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=34235@debbugs.gnu.org \
--cc=acm@muc.de \
--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).