all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <peter_dyballa@freenet.de>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 6127@debbugs.gnu.org
Subject: bug#6127: 24.0.50; crash because of missing font for menus
Date: Fri, 7 May 2010 23:22:43 +0200	[thread overview]
Message-ID: <3D0C342E-6E11-495B-B0D3-1389D01101A6@freenet.de> (raw)
In-Reply-To: <4BE3BAAF.5010005@swipnet.se>


Am 07.05.2010 um 09:01 schrieb Jan Djärv:

>
> I can't reproduce this.  Does it work if you remove that X resource,  
> or if you put in a font that exists?

Actually GNU Emacs always crashes! Also when the font is available  
*and* when I remove that X resource.


> You have to debug this.

The LOG file to that crash event contains

	Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
	Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0000017

It could be caused from the default X11 installation from (this time:  
almost) Apple (this problem comes up every few months, I think). So  
there is also a third party involved, particularly then GNU Emacs  
compiles and runs well with the X11 installation from MacPorts, which  
is up-to-date with development at Xorg. (Could I'm still awake in two  
hours...)


Debugging with GDB/GUD could go on: I have also Emacs.app, the non-X11  
windowing client.

--
Greetings

   Pete

Isn't vi that text editor with two modes... one that beeps and one  
that corrupts your file?
				– Dan Jacobson, on comp.os.linux.advocacy







  reply	other threads:[~2010-05-07 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 21:16 bug#6127: 24.0.50; crash because of missing font for menus Peter Dyballa
2010-05-07  7:01 ` Jan Djärv
2010-05-07 21:22   ` Peter Dyballa [this message]
2010-05-07 23:05   ` Peter Dyballa
2010-05-08 15:34     ` Jan Djärv

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=3D0C342E-6E11-495B-B0D3-1389D01101A6@freenet.de \
    --to=peter_dyballa@freenet.de \
    --cc=6127@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.