[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changes that should go into version 24.4

From: Daniel Colascione
Subject: Re: Changes that should go into version 24.4
Date: Fri, 21 Mar 2014 18:57:03 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

On 03/21/2014 06:47 PM, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I committed my changes that were waiting, then realized
> that two of them, in subr.el and battery.el, should probably
> go in the 24.4 release too.
> Would someone please put them in?

I can't speak to the battery.el change, but the subr.el one should be in
neither branch. It papers over a release-blocking bug. We shouldn't
release 24.4 until we've figured out why the hell the GC randomly
crashes. You can't even be sure that your lisp hack even fixes the problem.

Richard, it would be very helpful if you could provide either a recipe
for reproducing your crash or an actual crash dump (not your
paraphrasing of the stack trace).

Specifically, you've mentioned that the crash happens in mark_memory.
*Where* in mark_memory? What instruction? It doesn't make sense that
we'd fault accessing a stack slot on an active frame: doing so might
corrupt something later, sure, but that stack location is valid and
touching it isn't going to cause an immediate SIGSEGV.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]