all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Sharon Kimble <boudiccas@talktalk.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs 24.3.50 freezing in unusable state.
Date: Mon, 30 Sep 2013 11:21:17 +0200	[thread overview]
Message-ID: <3C34E49F-1F20-49C6-87CE-D7D62C5A20F6@Web.DE> (raw)
In-Reply-To: <20130930083841.3bc3dbe1@london>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Am 30.09.2013 um 09:38 schrieb Sharon Kimble:

> However, I have just downloaded and
> installed the latest emacs-snapshot, currently at 24.3.50.1, and that
> has started and loaded perfectly okay!

This *can* indicate that you are still using buggy GNU Emacs source code for building. (I fetch mine with bzr.)

Anyway, you have now the option to invoke report-emacs-bug or choose from the Help menu "Send Bug Report…". The eMail it creates has two interesting items for you: the configure options used to build that binary, which you could reuse for your own attempts to build a development (i.e., unstable, not guaranteed to work) version of GNU Emacs, and later a section "Load-path shadows". This is a list of ELisp files that override the default GNU Emacs Lisp files. It is possible that some of these "shadowing" files cause the error. The following code, put into some init file (your's or the system's), will report in the *Messages* buffer which ELisp file was loaded before the freeze happened:

	(defadvice load (before debug-log activate)
	  (message "(Tipp von Kai G) Lade jetzt: %s" (ad-get-arg 0)))

The German "Lade jetzt" means "Now loading". You could also insert into your init file

	(setq debug-on-error t)

that an ELisp debugger is started when an error is caught. It opens a *Backtrace* window in which, from bottom to top, it is listed how it happened that the error occurred.

In the case of a freeze it's of course best the *Messages* or the *Backtrace* buffer is displayed –  maybe this works by setting dedicated frame or window, but I have no idea how to achieve this. (I would probably use a (switch-to-buffer "*Messages*) statement before every line provoking a load of ELisp.)

- --
Greetings

  Pete

Experience is what you get when you don't get what you want.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlJJQo4ACgkQNkpl4NeD2QBQ+QCgjjscIFOTkVjl87G7FDGYUwo3
E9kAnArJlEAUqXJTis5GiCggmluEW0c4
=DGQB
-----END PGP SIGNATURE-----



  reply	other threads:[~2013-09-30  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28  8:53 emacs 24.3.50 freezing in unusable state Sharon Kimble
2013-09-28 16:16 ` Peter Dyballa
2013-09-28 17:03   ` Sharon Kimble
2013-09-28 17:46     ` Sharon Kimble
2013-09-28 18:20       ` Peter Dyballa
2013-09-28 18:33 ` Eli Zaretskii
2013-09-28 18:44   ` Sharon Kimble
2013-09-29 10:39   ` Sharon Kimble
2013-09-29 11:31     ` Peter Dyballa
2013-09-29 13:41       ` Sharon Kimble
2013-09-29 13:48         ` Mihamina Rakotomandimby
2013-09-29 14:07         ` Sean Sieger
2013-09-29 15:21         ` Peter Dyballa
2013-09-30  7:38           ` Sharon Kimble
2013-09-30  9:21             ` Peter Dyballa [this message]
2013-09-30 11:04               ` Sharon Kimble
2013-09-30 15:01                 ` Peter Dyballa

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=3C34E49F-1F20-49C6-87CE-D7D62C5A20F6@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=boudiccas@talktalk.net \
    --cc=help-gnu-emacs@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 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.