From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 16207@debbugs.gnu.org
Subject: bug#16207: 24.3.50; emacs_backtrace.txt
Date: Sat, 21 Dec 2013 18:15:14 +0100 [thread overview]
Message-ID: <52B5CCA2.1080406@gmx.at> (raw)
In-Reply-To: <CAAeL0SQaj_iTNSp1Rs6=jbcZM1-zQ_mD8TY9bLbBLnSzJPX6zg@mail.gmail.com>
> Breakpoint 1, terminate_due_to_signal (sig=22,
> backtrace_limit=2147483647) at emacs.c:351
> 351 signal (sig, SIG_DFL);
> (gdb) bt
> #0 terminate_due_to_signal (sig=22, backtrace_limit=2147483647) at emacs.c:351
> #1 0x011615dc in die (msg=0x148b198 "BUFFERP (a)", file=0x148b10c
> "lisp.h", line=874) at alloc.c:6742
> #2 0x010eb7fb in XBUFFER (a=58132514) at lisp.h:874
> #3 0x01089e14 in run_window_configuration_change_hook (f=0x3aa1a08
> <__register_frame_info+61479432>) at window.c:3257
...
> "set-window-configuration" (0x88db28)
The selected window doesn't have a buffer. I have no idea how to track
this down. Basically, we'd have to record in some variable a triple
<operation executed, selected window, its buffer> whenever we (1) select
a window, (2) delete a window, (3) kill a buffer, and check at strategic
positions (e.g. as above in run_window_configuration_change_hook)
whether this variable contains something fishy and put that variable's
value somewhere before aborting. Tedious ...
martin
next prev parent reply other threads:[~2013-12-21 17:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<efed9c40-3985-45be-81fd-22e7f8912725@default>
[not found] ` <<83fvpma6ie.fsf@gnu.org>
2013-12-21 16:22 ` bug#16207: 24.3.50; emacs_backtrace.txt Drew Adams
2013-12-21 18:38 ` Eli Zaretskii
[not found] ` <<fce2b6f2-11f6-400f-8ac6-382ab9a9d9bb@default>
[not found] ` <<83eh56a64m.fsf@gnu.org>
2013-12-21 16:27 ` Drew Adams
2013-12-21 16:53 ` Juanma Barranquero
2013-12-21 17:15 ` martin rudalics [this message]
2013-12-21 18:31 ` martin rudalics
2013-12-21 18:58 ` Eli Zaretskii
2013-12-21 19:40 ` martin rudalics
2013-12-21 18:45 ` Eli Zaretskii
2013-12-21 19:58 ` martin rudalics
2013-12-21 20:10 ` Eli Zaretskii
2013-12-22 15:37 ` martin rudalics
2013-12-22 15:39 ` Juanma Barranquero
2013-12-23 18:44 ` martin rudalics
2013-12-23 5:37 ` Drew Adams
2014-01-04 14:12 ` martin rudalics
2013-12-23 16:24 ` Eli Zaretskii
2013-12-23 18:44 ` martin rudalics
2013-12-21 18:46 ` Eli Zaretskii
2013-12-21 18:50 ` Juanma Barranquero
2013-12-21 18:52 ` Juanma Barranquero
2013-12-21 18:59 ` Eli Zaretskii
2013-12-21 16:56 ` Drew Adams
2013-12-20 21:38 Drew Adams
2013-12-20 21:53 ` Drew Adams
2013-12-21 9:46 ` Eli Zaretskii
2013-12-20 22:41 ` Juanma Barranquero
2013-12-21 9:38 ` 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=52B5CCA2.1080406@gmx.at \
--to=rudalics@gmx.at \
--cc=16207@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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.