unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jan.h.d@swipnet.se
Cc: 15575@debbugs.gnu.org
Subject: bug#15575: 24.3.50; New tty menus crash Emacs
Date: Fri, 11 Oct 2013 12:28:33 +0300	[thread overview]
Message-ID: <83iox4rwam.fsf@gnu.org> (raw)
In-Reply-To: <83fvs8p9ks.fsf@gnu.org>

> Date: Fri, 11 Oct 2013 10:09:55 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 15575@debbugs.gnu.org
> 
> Can you give me a login on that machine, with access to a directory
> where trunk is built?  I would like to debug this weird problem.

Sorry, no login is needed.  I was blind: the reason for the crash is
acutely visible in your backtrace:

  #4  0x000000000046dc26 in display_tty_menu_item (item_text=0xbf5224 <pure+2867940> "New Frame on Display...", width=40, face_id=15, x=0, y=24, submenu=0) at /home/jhd/src/emacs/current/src/xdisp.c:20648
                                                                                                                                           ^^^^

Note that y's value is 24.  Your terminal window has only 25 lines,
right?  I guess everyone else's, including mine, are taller.  The
"File" menu is longer than 24 lines, so the code is trying to write
beyond the end of the frame's glyph matrix, with predictably bad
results.

I will fix that ASAP.





  parent reply	other threads:[~2013-10-11  9:28 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
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 [this message]
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

  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=83iox4rwam.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 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).