From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 6075@debbugs.gnu.org
Subject: bug#6075: Lucid trunk build crashes at start
Date: Tue, 11 May 2010 15:48:02 -0400 [thread overview]
Message-ID: <jwv632u2r0b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4BDD39A1.4070602@swipnet.se> ("Jan Djärv"'s message of "Sun, 02 May 2010 10:36:49 +0200")
> I can't reproduce this.
Now, I sometimes can and sometimes can't. Still investigating.
> I used your configure flags, and tried with Xaw3d and straight Xaw.
> I guess it is some memory corruption or aligment problem.
I saw it on all my machines (tho admittedly, they're all running pretty
much the same Debian testing). I tried "xrdb -remove" but it didn't help.
> Can you compile without Xaw3d and just use standard Xaw?
You mean without-toolkit-scroll-bars? Good idea...
Hmm... configure still says "Does Emacs use -lXaw3d? yes".
But I'm not sure yet if it helps (I haven't seen it crash
without-toolkit-scroll-bars, but since then I haven't seen it crash on
that same machine with Xaw3d scroll bars either).
> You don't have that gcc 4.4 memcpy bug?
You mean the 4.5 bug? No, I have Debian's 4.4.2.
> Does it happen wih -O0 also?
Yup.
> If you compiled Xaw3d yourself, recompile it with debug and run gdb to
> the crash.
The crash I showed was with a hand-compiled Xaw3d with debug info
(actually an Xaw3d with some local changes so that you can dynamically
choose the Xaw-style or the motif-arrow-style scrollbars). But the
backtrace is in Xt code, not in Xaw(3d) code.
Stefan
next prev parent reply other threads:[~2010-05-11 19:48 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
2010-05-11 19:48 ` Stefan Monnier [this message]
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=jwv632u2r0b.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6075@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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.