all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15575@debbugs.gnu.org
Subject: bug#15575: 24.3.50; New tty menus crash Emacs
Date: Thu, 10 Oct 2013 19:35:30 +0200	[thread overview]
Message-ID: <5AFF19E5-0778-425A-AF0C-0C027DEFB3D6@swipnet.se> (raw)
In-Reply-To: <83txgpp0f1.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

Hello.

10 okt 2013 kl. 18:15 skrev Eli Zaretskii <eliz@gnu.org>:

>> 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];  <<<<<<<<<<<<<<
> 

It is the same place in the code, but not the same line in the file.

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

On Fedora 19:

(gdb) p area
$1 = 1
(gdb) p i
$2 = 0
(gdb) 

> 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?

No, I did not.  I usually don't because the checkings more often than not trip on something that really isn't a bug.  I've never caught a real error with it.

This one triggers:

#3  0x0000000000449d2b in deep_copy_glyph_row (from=<optimized out>, 
    to=0xce9e40) at /home/jhd/src/emacs/current/src/xdisp.c:20597
20597	  eassert (to->used[0] == from->used[0]);

(gdb) p to->used[0]
$1 = -15072

There is some memory corruption.  If I press F11 twice and then F10, the crash does not happen. The menu appears but there are major redrawing problems, for example, going down in the menu does not work, it just scrolls the buffer instead until the menu disappears over the top, the buffer is not redrawn correctly when the menu goes away, nor is the menu bar.  I did not test it much.
Could be another symptom of the memory corruption.

	Jan D.





[-- Attachment #2.1: Type: text/html, Size: 3484 bytes --]

[-- Attachment #2.2: screen1.png --]
[-- Type: image/png, Size: 43445 bytes --]

[-- Attachment #2.3: screen2.png --]
[-- Type: image/png, Size: 33008 bytes --]

  reply	other threads:[~2013-10-10 17:35 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 [this message]
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=5AFF19E5-0778-425A-AF0C-0C027DEFB3D6@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=15575@debbugs.gnu.org \
    --cc=eliz@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.