GNU bug report logs -
#16207
24.3.50; emacs_backtrace.txt
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Fri, 20 Dec 2013 21:40:03 UTC
Severity: normal
Found in version 24.3.50
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
Message #41 received at 16207 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 21 Dec 2013 18:15:14 +0100
> From: martin rudalics <rudalics <at> gmx.at>
> Cc: 16207 <at> debbugs.gnu.org
>
> > 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.
Maybe one way is to think how could this happen, ever. How can such
window even exist?
This bug report was last modified 11 years and 195 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.