[Top][All Lists]

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

wrong behaviour of <struct frame>

From: alin soare
Subject: wrong behaviour of <struct frame>
Date: Thu, 2 Dec 2010 08:54:10 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

I defined within the struct frame an integer variable

int ct;

If I define it immediately after the menu_bar_vector, it is initialized
somewhere with the pointer value of Qnil. (&Qnil)

      Only the X toolkit version uses this.  */

   Lisp_Object menu_bar_vector;
+    int ct;

In this case, if I change the value f->ct, emacs crashes with segmentation
fault, generated by the garbage collector. Why , as time as I initialize a
variable defined by myself ?


If I define it at the end of struct frame, id est immediately after the

/* All display backends seem to need these two pixel values. */
  unsigned long background_pixel;
  unsigned long foreground_pixel;
+    int ct;

everything works fine in that case.

I wish to ask you to suggest me if you can, what happens when I define the var.
'ct' inside the struct frame.


reply via email to

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