From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: unicode-2 branch segfaulting on MacOS X?
Date: Mon, 23 Oct 2006 10:04:52 +0900 [thread overview]
Message-ID: <E1GboFI-0002la-00@etlken> (raw)
In-Reply-To: <ehg36a$si9$1@sea.gmane.org> (message from Geoffrey Alan Washburn on Sun, 22 Oct 2006 11:36:42 -0400)
In article <ehg36a$si9$1@sea.gmane.org>, Geoffrey Alan Washburn <geoffw@cis.upenn.edu> writes:
> I've been trying to get the latest revision of the emacs-unicode-2
> branch to build and run under MacOS X. Building seems to work fine,
> I've been using the following configuration
> ./configure --prefix=/local --enable-font-backend --with-gtk --with-xft
> --with-tiff --with-ungif --with-xpm --enable-asserts CPPFLAGS=-idirafter
> /usr/X11R6/include
> However, when I attempt to invoke emacs with
> emacs --enable-font-backend --font "Bitstream Vera Sans Mono-16"
> it seems to be segfaulting somewhere in font_unparse_fcname. Any ideas?
I can't reproduce it on GNU/Linux. So, could you please use
gdb to find exactly where (and how) Emacs causes segfault
(see etc/DEBUG if you are not familiar with gdb).
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-10-23 1:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 15:36 unicode-2 branch segfaulting on MacOS X? Geoffrey Alan Washburn
2006-10-23 1:04 ` Kenichi Handa [this message]
2006-10-23 1:17 ` Geoffrey Alan Washburn
2006-10-23 2:45 ` Kenichi Handa
2006-10-23 3:32 ` Geoffrey Alan Washburn
2006-10-23 5:59 ` Kenichi Handa
2006-10-23 10:00 ` Geoffrey Alan Washburn
2006-10-23 11:26 ` Kenichi Handa
2006-10-23 12:55 ` Geoffrey Alan Washburn
2006-10-27 4:17 ` Kenichi Handa
2006-10-27 10:05 ` Geoffrey Alan Washburn
2006-10-27 7:38 ` Kenichi Handa
2006-10-27 13:36 ` Geoffrey Alan Washburn
2006-10-28 0:41 ` Giorgos Keramidas
2006-10-28 0:43 ` Giorgos Keramidas
2006-10-28 17:39 ` Geoffrey Alan Washburn
2006-11-03 16:43 ` Geoffrey Alan Washburn
2006-11-08 11:55 ` Kenichi Handa
2006-11-08 19:23 ` Geoffrey Alan Washburn
2006-11-09 3:20 ` stephen
2006-11-09 11:41 ` Kenichi Handa
2006-11-12 2:59 ` Geoffrey Alan Washburn
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=E1GboFI-0002la-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.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).