From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: alin soare Newsgroups: gmane.emacs.devel Subject: wrong behaviour of Date: Thu, 2 Dec 2010 08:54:10 +0000 (UTC) Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1291280424 21588 80.91.229.12 (2 Dec 2010 09:00:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Dec 2010 09:00:24 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 02 10:00:17 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PO51V-0005FQ-4f for ged-emacs-devel@m.gmane.org; Thu, 02 Dec 2010 10:00:17 +0100 Original-Received: from localhost ([127.0.0.1]:46289 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PO51V-0007BB-0b for ged-emacs-devel@m.gmane.org; Thu, 02 Dec 2010 04:00:17 -0500 Original-Received: from [140.186.70.92] (port=49831 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PO51N-00074A-FZ for emacs-devel@gnu.org; Thu, 02 Dec 2010 04:00:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PO51K-0002Hd-Ei for emacs-devel@gnu.org; Thu, 02 Dec 2010 04:00:08 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:57761) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PO51K-0002HF-5y for emacs-devel@gnu.org; Thu, 02 Dec 2010 04:00:06 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PO51I-0005Ba-82 for emacs-devel@gnu.org; Thu, 02 Dec 2010 10:00:04 +0100 Original-Received: from 82-76-35-107.rdsnet.ro ([82-76-35-107.rdsnet.ro]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Dec 2010 10:00:04 +0100 Original-Received: from as1789 by 82-76-35-107.rdsnet.ro with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Dec 2010 10:00:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 41 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 82.76.35.107 (Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.2.12) Gecko/20101027 Ubuntu/10.04 (lucid) Firefox/3.6.12) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:133307 Archived-At: 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 fieldforeground_pixel, /* 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. Alin.