all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 15575@debbugs.gnu.org
Subject: bug#15575: 24.3.50; New tty menus crash Emacs
Date: Thu, 10 Oct 2013 19:15:30 +0300	[thread overview]
Message-ID: <83txgpp0f1.fsf@gnu.org> (raw)
In-Reply-To: <97F9A2CA-8E08-4867-93C3-5BAE8DF80D72@swipnet.se>

> From: Jan Djärv <jan.h.d@swipnet.se>
> Date: Thu, 10 Oct 2013 10:06:51 +0200
> 
> 9 okt 2013 kl. 21:00 skrev Eli Zaretskii <eliz@gnu.org>:
> > 
> > Can you try the patch below?
> 
> Makes no difference on OSX or Fedora 19, still crashes in the same place.

How do you mean "the same place"?  That place should no longer exist
after applying the patch.

If you mean the line marked below:

  /* Count how many glyphs to copy and copy the glyphs.  */
  for (area = LEFT_MARGIN_AREA; area < LAST_AREA; ++area)
    for (i = 0; i < from->used[area]; i++)
      to->glyphs[area][i] = from->glyphs[area][i];  <<<<<<<<<<<<<<

then please tell what is the value of 'area' and of 'i' at the point
of the crash.

Btw, did you compile with --enable-checking, i.e. were the 3 eassert
statements at the beginning of deep_copy_glyph_row compiled into the
program?





  parent reply	other threads:[~2013-10-10 16:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 17:05 bug#15575: 24.3.50; New tty menus crash Emacs Jan Djärv
2013-10-09 17:41 ` Eli Zaretskii
2013-10-09 17:58   ` Jan Djärv
2013-10-09 18:17     ` Jan Djärv
2013-10-09 18:20       ` Jan Djärv
2013-10-09 19:00     ` Eli Zaretskii
     [not found]       ` <97F9A2CA-8E08-4867-93C3-5BAE8DF80D72@swipnet.se>
2013-10-10 16:15         ` Eli Zaretskii [this message]
2013-10-10 17:35           ` Jan Djärv
2013-10-10 19:36             ` Eli Zaretskii
2013-10-11  5:44               ` Jan Djärv
2013-10-11  7:09                 ` Eli Zaretskii
2013-10-11  8:10                   ` Eli Zaretskii
2013-10-11  9:28                   ` Eli Zaretskii
2013-10-11 11:06                     ` Eli Zaretskii
2013-10-11 16:39                       ` Jan Djärv
2013-10-11 17:29                         ` Eli Zaretskii
2013-10-11 18:53                           ` Jan Djärv
2013-10-11 11:12                     ` Jan Djärv
2013-10-11  9:55                   ` martin rudalics
2013-10-11 11:09                     ` Eli Zaretskii
2013-10-11 11:42                       ` martin rudalics
2013-10-11 11:53                         ` martin rudalics
2013-10-11 12:04                           ` Dani Moncayo
2013-10-11 14:25                             ` Eli Zaretskii
2013-10-11 14:43                               ` Dani Moncayo
2013-10-11 14:54                                 ` Eli Zaretskii
2013-10-11 15:02                                   ` Dani Moncayo
2013-10-11 15:44                                     ` Eli Zaretskii
2013-10-11 16:37                                       ` Dani Moncayo
2013-10-11 14:20                           ` Eli Zaretskii
2013-10-15 18:27                             ` martin rudalics
2013-10-11 14:17                         ` Eli Zaretskii
2013-10-11 18:22                           ` Eli Zaretskii
2013-10-11 18:49                             ` Stefan Monnier
2013-10-11 20:26                               ` Eli Zaretskii
2013-10-15 18:27                           ` martin rudalics
2013-10-15 19:01                             ` Eli Zaretskii
2013-10-16  7:44                               ` martin rudalics
2013-10-16 15:21                                 ` Eli Zaretskii
2013-10-16 17:48                                   ` martin rudalics
2013-10-16 18:34                                     ` Eli Zaretskii
2013-10-16 18:45                                       ` martin rudalics
2013-10-10 20:56             ` Stefan Monnier
2013-10-10 20:59               ` Eli Zaretskii

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=83txgpp0f1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15575@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.