bug#28700: 25.2; Cannot kill Eshell buffer

[Noam Postavsky]

On Wed, Oct 4, 2017 at 10:13 AM, Live System User <nyc4bos@aol.com> wrote:
>> Can you get a backtrace if you M-x toggle-debug-on-error RET?
>
>          Ufortunately no;
>
> debug-on-error is a variable defined in ‘C source code’.
> Its value is t
> Original value was nil
>
>
>          Only that *Message* buffer imfomation.

Does setting debug-on-message set to "Text is read-only" help?
Or with debug-on-signal set to t? (You might have to continue ('c' in
the *Backtrace* buffer) if you hit some unrelated errors that are
normally suppressed)