[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs
From: |
martin rudalics |
Subject: |
bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs |
Date: |
Fri, 19 Mar 2021 10:18:33 +0100 |
> Sorry, I don't understand: when kill-buffer kills the current buffer,
> it replaces it with another one. Are you saying we have a way of
> killing buffers that bypasses kill-buffer? if so, can you describe how
> that can be done?
>
> Or what else am I missing?
Redisplay occasionally does things like
saved_current_buffer = current_buffer;
current_buffer = XBUFFER (w->contents);
...
current_buffer = saved_current_buffer;
What if ... killed saved_current_buffer?
martin
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, (continued)
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/31
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Eli Zaretskii, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Eli Zaretskii, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Michael Welsh Duggan, 2021/03/29
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, martin rudalics, 2021/03/19
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Eli Zaretskii, 2021/03/19
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs,
martin rudalics <=
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, martin rudalics, 2021/03/19
- bug#47244: 28.0.50; SIGSEGV in long-runnning Emacs, Eli Zaretskii, 2021/03/19