GNU bug report logs - #6155
Crashes on w32 because of bad frame initialization

Previous Next

Package: emacs;

Reported by: Lennart Borgman <lennart.borgman <at> gmail.com>

Date: Mon, 10 May 2010 14:16:02 UTC

Severity: normal

Tags: moreinfo

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

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

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 6155 <at> debbugs.gnu.org
Subject: Re: bug#6155: Crashes on w32 because of bad frame initialization
Date: Mon, 10 May 2010 18:00:57 +0200

On Mon, May 10, 2010 at 5:12 PM, Juanma Barranquero <lekktu <at> gmail.com> wrote:
>> I have seen numerous crashes on w32 when a frame has been badly
>> initialized. I wonder if the problem is that frames can get half
>> initialized.
>>
>> In the function Fx_create_frame a bad value coming from a frame
>> parameter (menu-bar-lines . t) will lead to an error in
>>
>>  x_default_parameter (f, parameters, Qmenu_bar_lines, make_number (1),
>>                       "menuBar", "MenuBar", RES_TYPE_NUMBER);
>>
>> Does not that leave the frame half initialized?
>
> Do you have a recipe to reproduce the problem'

I have no exact recipe but I noticed the problem when the above
parameter was in the list of parameters to make frame.

The `t' in (menu-bar-lines . t) shoudld be a number. In make-frame I
got an error and shortly afterwards Emacs crashed.
This bug report was last modified 13 years and 319 days ago.

Previous Next

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