[Emacs-bug-tracker] bug#6155: closed (Crashes on w32 because of bad frame initialization)

[GNU bug Tracking System]

Your message dated Mon, 11 Jul 2011 19:16:31 -0400
with message-id <address@hidden>
and subject line Re: bug#6155: Crashes on w32 because of bad frame 
initialization
has caused the GNU bug report #6155,
regarding Crashes on w32 because of bad frame initialization
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
6155: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6155
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Crashes on w32 because of bad frame initialization
>
>
>
>
> Date: 
>
> Mon, 10 May 2010 16:13:15 +0200
>
>
>
>
> 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?
>
> (I am loooking at the code from a trunk checkout done 2010-05-06.)
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#6155: Crashes on w32 because of bad frame initialization
>
>
>
>
> Date: 
>
> Mon, 11 Jul 2011 19:16:31 -0400
>
>
>
>
> User-agent: 
>
> Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
>
>
>
>
> In the absence of a recipe to reproduce the issue or a backtrace from a
> crash (from a vanilla Emacs with debugging info) I don't think anything
> can be done. Please reopen or reply to this report if you get either of
> those.
>
>
> --- End Message ---