GNU bug report logs - #16901
24.3.50; emacs_backtrace.txt

Previous Next

Full log

Message #46 received at 16901 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16901 <at> debbugs.gnu.org, dmantipov <at> yandex.ru, drew.adams <at> oracle.com
Subject: Re: bug#16901: 24.3.50; emacs_backtrace.txt
Date: Sat, 01 Mar 2014 09:15:41 +0200

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Fri, 28 Feb 2014 18:12:57 +0100
> Cc: Eli Zaretskii <eliz <at> gnu.org>, Dmitry Antipov <dmantipov <at> yandex.ru>, 16901 <at> debbugs.gnu.org
> 
> > Maybe some development
> > just before that build is responsible?
> 
> These are the changes between the previous snapshot and the build from
> Feb 22, except for the ones obviously unrelated (doc fixes, manual,
> tests, etc.).

Thanks; I see nothing that immediately stands out.  It could be an
unrelated change which just exposed a bug that was present previously.

Or it could be some change in Drew's use patterns, like in the
window/frame configurations and other customizations, which exposed an
extant bug.  Or even some changes in the OS and other programs used in
conjunction with Emacs, for that matter.

IOW, there's no way to be certain without a recipe, or something like
that.

Previous Next

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