unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 8217@debbugs.gnu.org
Subject: bug#8217: 23.3; Runtime segmentation fault when compiled with -O2 on GNU/Linux
Date: Thu, 24 Mar 2011 12:26:10 -0400	[thread overview]
Message-ID: <87ei5web8d.fsf@stupidchicken.com> (raw)
In-Reply-To: <19832.48987.620735.717352@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Thu, 10 Mar 2011 13:08:59 +0100")

Ulrich Mueller <ulm@gentoo.org> writes:

>> FWIW, I cannot reproduce this on this system:
>
>>   Linux fencepost 2.6.32-313-ec2 #26-Ubuntu SMP Fri Feb 11 22:34:31
>> UTC 2011 x86_64 GNU/Linux
>
>> [...]
>
>> with GTK+ Version 2.20.1 as the toolkit.
>
> I confirm that it doesn't fail for me if I configure --with-toolkit=gtk.
> The segfault occurs with the --with-toolkit=athena configure option.

I think this has to do with the messy way we handle scroll bars, which
are currently stored as Lisp objects and recast into scroll_bar
structures when used.

By the way, I notice that x_scroll_bar_create has

  struct scroll_bar *bar
    = ALLOCATE_PSEUDOVECTOR (struct scroll_bar, x_window, PVEC_OTHER);

I don't know if the former is correct (it was introduced back in
revision 82084 by Stefan), but it means the SCROLL_BAR_VEC_SIZE macro
defined in xterm.h is unused, which looks odd.  In comparison, w32term.c
has

  struct scroll_bar *bar
    = XSCROLL_BAR (Fmake_vector (make_number (SCROLL_BAR_VEC_SIZE), Qnil));





  reply	other threads:[~2011-03-24 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  8:34 bug#8217: 23.3; Runtime segmentation fault when compiled with -O2 on GNU/Linux Ulrich Mueller
2011-03-10  8:52 ` Andreas Schwab
     [not found]   ` <19832.41051.618372.463060@a1i15.kph.uni-mainz.de>
     [not found]     ` <19832.49227.947125.153989@a1i15.kph.uni-mainz.de>
2011-03-10 18:39       ` Glenn Morris
2011-03-10 11:48 ` Eli Zaretskii
2011-03-10 12:08   ` Ulrich Mueller
2011-03-24 16:26     ` Chong Yidong [this message]
2011-03-25  1:17       ` Stefan Monnier
2016-08-05  1:28     ` npostavs
2016-08-06 13:29       ` Ulrich Mueller
2016-08-06 13:34         ` npostavs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ei5web8d.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=8217@debbugs.gnu.org \
    --cc=ulm@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).