all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 6075@debbugs.gnu.org
Subject: bug#6075: Lucid trunk build crashes at start
Date: Sun, 02 May 2010 10:36:49 +0200	[thread overview]
Message-ID: <4BDD39A1.4070602@swipnet.se> (raw)
In-Reply-To: <jwvy6g2lvcv.fsf@iro.umontreal.ca>



Stefan Monnier skrev 2010-05-02 07.34:
> Package: Emacs
> Version: 24.0.50
>
> My Lucid build of Emacs crashes right at the start before any frame gets
> opened (emacs -nw works fine):
>
>     (gdb) r -Q
>     Starting program: /home/monnier/src/emacs/bzr/trunk/src/emacs -Q
>     [Thread debugging using libthread_db enabled]
>
>     Program received signal SIGSEGV, Segmentation fault.
>     0xb7f1cad0 in XtInitializeWidgetClass () from /usr/lib/libXt.so.6
>     (gdb) bt
>     #0  0xb7f1cad0 in XtInitializeWidgetClass () from /usr/lib/libXt.so.6
>     #1  0xb7f1daf8 in _XtCreateWidget () from /usr/lib/libXt.so.6
>     #2  0xb7f1dea4 in XtCreateWidget () from /usr/lib/libXt.so.6
>     #3  0x081ea276 in x_window (f=0x8a7c0b0, window_prompting=0,
>         minibuffer_only=0) at xfns.c:2530

I can't reproduce this.  I used your configure flags, and tried with Xaw3d and 
straight Xaw.  I guess it is some memory corruption or aligment problem.  Can 
you compile without Xaw3d and just use standard Xaw?  You don't have that gcc 
4.4 memcpy bug?  Does it happen wih -O0 also?

If you compiled Xaw3d yourself, recompile it with debug and run gdb to the crash.

	Jan D.






  reply	other threads:[~2010-05-02  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02  5:34 bug#6075: Lucid trunk build crashes at start Stefan Monnier
2010-05-02  8:36 ` Jan Djärv [this message]
2010-05-11 19:48   ` Stefan Monnier
2010-05-12  6:04     ` Jan Djärv
2010-12-06 20:37 ` Chong Yidong
2010-12-06 21:37   ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=4BDD39A1.4070602@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=6075@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.