unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Killing a frame sometimes kills emacs
Date: Thu, 01 Sep 2011 06:27:21 -0400	[thread overview]
Message-ID: <E1Qz4UT-0007nc-RY@fencepost.gnu.org> (raw)
In-Reply-To: <871uw04lr9.fsf@thinkpad.tsdh.de> (message from Tassilo Horn on Thu, 01 Sep 2011 12:09:30 +0200)

> From: Tassilo Horn <tassilo@member.fsf.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 01 Sep 2011 12:09:30 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> Hi Eli,
> 
> >> From: Tassilo Horn <tassilo@member.fsf.org>
> >> Date: Wed, 31 Aug 2011 22:16:55 +0200
> >> 
> >> Do you have any suggestions on how to debug this issue?
> >
> > Run Emacs under a debugger, put a breakpoint on Fkill_emacs, and when
> > this happens again, tell use who called it by showing the backtrace.
> 
> It turned out to be a crash, not something calling Fkill_emacs.  Here's
> the backtrace:

What about the Lisp backtrace?  And since this is an optimized build,
the backtrace is almost useless anyway.  Can you try reproducing this
in an unoptimized build?

> #7  0x00000000004e157c in xg_display_close (dpy=0x6ca0020) at gtkutil.c:182
>         gdpy = 0xd682e0
> #8  0x00000000004afc49 in x_delete_terminal (terminal=<optimized out>)
>     at xterm.c:10607
>         dpyinfo = 0x698d3e0
> #9  0x00000000004a40f2 in Fdelete_terminal (terminal=107998581, 
>     force=<optimized out>) at terminal.c:345
>         t = 0x66fed70
> #10 0x00000000004235cc in delete_frame (frame=99991829, force=<optimized out>)
>     at frame.c:1379
>         tmp = <optimized out>
>         terminal = <optimized out>
>         f = 0x5f5c110
>         sf = 0x121b7e0
>         kb = 0x0
>         minibuffer_selected = 0
>         tooltip_frame = 0
> #11 0x000000000042382a in Fdelete_frame (frame=<optimized out>, 
>     force=<optimized out>) at frame.c:1516

This part does look as if Emacs was going to close the X display where
the frame was displayed.  Were all other frames in that session on
other displays?  If not, how come Emacs is about to delete the
terminal?  Here's the relevant code:

    if (terminal->reference_count == 0)
      {
	Lisp_Object tmp;
	XSETTERMINAL (tmp, terminal);

        kb = NULL;
	Fdelete_terminal (tmp, NILP (force) ? Qt : force);
      }

Can you look at the value of terminal->reference_count?



  reply	other threads:[~2011-09-01 10:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 20:16 Killing a frame sometimes kills emacs Tassilo Horn
2011-08-31 20:51 ` joakim
2011-08-31 23:06 ` chad
2011-09-01  2:53 ` Eli Zaretskii
2011-09-01  7:04   ` Tassilo Horn
2011-09-01 10:09   ` Tassilo Horn
2011-09-01 10:27     ` Eli Zaretskii [this message]
2011-09-01 10:42       ` Tassilo Horn
2011-09-01 10:56         ` Eli Zaretskii
2011-09-01 11:09           ` Tassilo Horn
2011-09-01 10:33     ` Andreas Schwab
2011-09-01 10:45       ` Tassilo Horn
2011-09-01 12:47         ` Jan D.
2011-09-01 13:05           ` Tassilo Horn
2011-09-01 15:29           ` Eli Zaretskii
2011-09-01 19:30             ` Ken Raeburn
2011-09-02 15:02               ` Andreas Schwab
2011-10-11  6:46             ` Tassilo Horn
2011-10-11 12:53               ` Stefan Monnier
2011-10-11 14:53                 ` Tassilo Horn
2011-10-11 17:38                   ` James Cloos
2011-10-11 19:17                     ` Tassilo Horn
2011-10-11 19:49                       ` Tassilo Horn
2011-10-12  2:04                     ` Chong Yidong
2011-10-12  6:49                       ` Tassilo Horn
2011-10-12 12:57                         ` Stefan Monnier
2011-11-17 10:10                           ` Tassilo Horn
2011-11-17 11:18                             ` Chong Yidong
2011-11-17 13:45                               ` Tassilo Horn
2011-11-17 16:34                                 ` Paul Eggert
2011-11-17 16:58                                   ` Tassilo Horn
2011-11-18  2:41                                   ` Chong Yidong
2011-11-18  2:05                             ` Stefan Monnier
2011-11-18  9:38                               ` Tassilo Horn
2012-01-20 23:29                                 ` andres.ramirez
2012-01-21  0:34                                   ` Glenn Morris
2012-01-21  8:02                                     ` andres.ramirez
2012-01-20 23:29                                 ` andres.ramirez
2011-10-11 17:56               ` Jan Djärv

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=E1Qz4UT-0007nc-RY@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tassilo@member.fsf.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).