GNU bug report logs - #33498
26.1; Unable to delete minibuffer-only+child frames

Previous Next

Full log

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 33498 <at> debbugs.gnu.org
Subject: Re: bug#33498: 26.1; Unable to delete minibuffer-only+child frames
Date: Wed, 6 Mar 2019 11:07:14 -0800

[Message part 1 (text/plain, inline)]

> I think I fixed this now on master.  Please have a look.

Unfortunately the fix broke builds configured with
--enable-gcc-warnings, as GCC complains about the use of an
uninitialized variable that appears to be a typo in the fix. I installed
the attached patch to unbreak the build; please check it to make sure
that I understood the intent of the fix correctly.

It's a good idea to use './configure --enable-gcc-warnings' when making
changes to the C code in Emacs, as GCC is reasonably good at catching
typos like this, and typically does not generate too many false alarms.

[0001-Fix-typo-in-fix-for-Bug-33498.patch (text/x-patch, attachment)]

Previous Next

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