all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: emacs crashed on windows-xp
Date: Thu, 12 Oct 2006 16:04:57 +0200	[thread overview]
Message-ID: <m3k6354ol2.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <452D1379.7010307@gnu.org> (Jason Rumney's message of "Wed\, 11 Oct 2006 16\:53\:29 +0100")

Jason Rumney <jasonr@gnu.org> writes:

>>> It crashes with a message print out:
>>>         Fatal error (11)Segmentation fault
>>>
>>> I'm running emacs-unicode-2 (CVS:2006-10-04) in Fedora core 5.
>>>     
>>
>> Doesn't happen for me with CVS trunk on GNU/Linux (redhat 9.0).
>>   
>
> Strange, it does for me on GNU/Linux (Debian testing) as well as Windows..
>
> Did you follow the exact formula Zhang Wei posted (across two
> different mails)?
>
>    emacs -Q
>
>    M-: (setq frame-title-format (list "%f (%l,%c) ---- @" system-name))
>
>    C-h i m elisp <RET> m lists <RET> m rings <RET> u u


I looked briefly at this (don't have time to dig further right now).

It seems that the problem is that in redisplay_internal, the frame title is
drawn _before_ the windows are updated, so the stuff which depends on 
actual window contents (such as %l) may fail to render properly -- and
even crash emacs as we have seen here.

Perhaps a simple fix would be to move the call to x_consider_frame_title
currently inside prepare_menu_bars to after we have completed the
window updates...

Unfortunately, this comment says this is not TRT ... so what is TRT?

  /* Update all frame titles based on their buffer names, etc.  We do
     this before the menu bars so that the buffer-menu will show the
     up-to-date frame titles.  */

BTW, what does frame titles have to do with the buffer menu?


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  parent reply	other threads:[~2006-10-12 14:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <u3b9vs3d0.fsf@gmail.com>
     [not found] ` <E1GXZXq-00010B-E1@fencepost.gnu.org>
     [not found]   ` <uu02bdxx0.fsf@gmail.com>
     [not found]     ` <E1GXb1L-0006rN-Kp@fencepost.gnu.org>
     [not found]       ` <m23b9vjgrh.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found]         ` <m3ejtf7yh0.fsf@kfs-l.imdomain.dk>
2006-10-11 15:53           ` emacs crashed on windows-xp Jason Rumney
2006-10-11 16:32             ` Jan Djärv
2006-10-12  6:52               ` emacs crashed on many OSes (was: emacs crashed on windows-xp) Jan Djärv
2006-10-12 17:52                 ` Giorgos Keramidas
2006-10-12 19:12                   ` emacs crashed on many OSes Jan D.
2006-10-12 22:43                     ` Giorgos Keramidas
2006-10-12 13:50             ` emacs crashed on windows-xp Kim F. Storm
2006-10-12 14:04             ` Kim F. Storm [this message]
2006-10-12 14:57               ` Eli Zaretskii
2006-10-12 15:22               ` Stefan Monnier
2006-10-12 22:38               ` Richard Stallman
2006-10-12 23:11                 ` Kim F. Storm
2006-10-13 11:19                   ` Richard Stallman
2006-10-13  2:50                 ` Chong Yidong
2006-10-13  8:25                   ` Kim F. Storm
2006-10-13 11:01                   ` Jason Rumney
2006-10-13 15:48                     ` Eli Zaretskii
2006-10-13 16:56                       ` Chong Yidong
2006-10-13 19:08                         ` Eli Zaretskii
2006-10-13 11:19                   ` Richard Stallman
2006-10-13 14:28                     ` Chong Yidong

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=m3k6354ol2.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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 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.