unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 17386@debbugs.gnu.org
Subject: bug#17386: 24.3.90; emacs_abort in cmcheckmagic
Date: Wed, 28 May 2014 10:35:39 +0200	[thread overview]
Message-ID: <87egzexpus.fsf@geodiff-mac3.ulb.ac.be> (raw)
In-Reply-To: <874n18ydh9.fsf@geodiff-mac3.ulb.ac.be> (Nicolas Richard's message of "Fri, 02 May 2014 07:08:18 +0200")

It happened again (at least it looks very very similar to me) but I'm
afraid I'm not bringing much new information.

Anyway, just to show that it is the same problem :

(gdb) f 2
#2  0x0812f9b7 in cmcheckmagic (tty=0x897de50) at cm.c:120
120             emacs_abort ();
(gdb) l
115     cmcheckmagic (struct tty_display_info *tty)
116     {
117       if (curX (tty) == FrameCols (tty))
118         {
119           if (!MagicWrap (tty) || curY (tty) >= FrameRows (tty) - 1)
120             emacs_abort ();
121           if (tty->termscript)
122             putc ('\r', tty->termscript);
123           putc ('\r', tty->output);
124           if (tty->termscript)
(gdb) p curY(tty)
$1 = 41
(gdb) p FrameRows(tty)
$2 = 23

The situation was as follows: I had a detached tmux session with an
"emacs -nw" in it (in gdb), and I had a graphical frame open also (via
emacsclient). I then tried to reattach to the tmux session, and that's
when emacs crashed.

I guess it would help to know what happens when tmux is detached.
Perhaps emacs should receive some kind of notification, and that doesn't
happen in some cases ? Next time I have to close emacs I'll try using
screen instead of tmux.

-- 
Nico.





  parent reply	other threads:[~2014-05-28  8:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02  5:08 bug#17386: 24.3.90; emacs_abort in cmcheckmagic Nicolas Richard
2014-05-02  7:28 ` Eli Zaretskii
2014-05-02  8:14   ` Nicolas Richard
2014-05-02  8:58     ` Eli Zaretskii
2014-05-02  9:45       ` Nicolas Richard
2014-05-02 12:09         ` Eli Zaretskii
2014-05-02 15:17           ` Nicolas Richard
2014-05-02 15:42             ` Eli Zaretskii
2014-05-02 16:00               ` Nicolas Richard
2014-05-02 16:17                 ` Eli Zaretskii
2014-05-03  6:56                   ` Nicolas Richard
2014-05-03  7:18                     ` Eli Zaretskii
2014-05-03  8:21                       ` Andreas Schwab
2014-05-03  8:53                         ` Eli Zaretskii
2014-05-03  8:56                           ` Andreas Schwab
2014-05-03  9:16                             ` Eli Zaretskii
2014-05-05 10:27                               ` Nicolas Richard
2014-05-05 11:11                                 ` Eli Zaretskii
2014-05-05 11:25                                   ` Nicolas Richard
2014-05-28  8:35 ` Nicolas Richard [this message]
2014-05-28 14:17   ` Eli Zaretskii
2014-05-28 14:41     ` Nicolas Richard
2014-05-28 15:24       ` Andreas Schwab
2014-05-28 16:27         ` Eli Zaretskii
2014-05-28 16:38           ` Andreas Schwab
2014-05-28 20:47           ` Nicolas Richard
2014-05-29 16:05             ` Eli Zaretskii
2022-04-26 12:56 ` Lars Ingebrigtsen
2022-04-29  7:26   ` Nicolas Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 10:10     ` Lars Ingebrigtsen

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=87egzexpus.fsf@geodiff-mac3.ulb.ac.be \
    --to=theonewiththeevillook@yahoo.fr \
    --cc=17386@debbugs.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 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).