GNU bug report logs -
#28700
25.2; Cannot kill Eshell buffer
Previous Next
Reported by: Live System User <nyc4bos <at> aol.com>
Date: Wed, 4 Oct 2017 09:58:01 UTC
Severity: minor
Tags: fixed, patch
Merged with 29153
Found in versions 25.2, 25.3
Fixed in version 26.1
Done: Noam Postavsky <npostavs <at> users.sourceforge.net>
Bug is archived. No further changes may be made.
Full log
Message #35 received at 28700 <at> debbugs.gnu.org (full text, mbox):
Noam Postavsky <npostavs <at> users.sourceforge.net> writes:
> On Wed, Oct 4, 2017 at 3:50 PM, Live System User <nyc4bos <at> aol.com> wrote:
>> Can you give me step-by-step instructions?
>>
>> BTW, is it possible to Edebug `kill-buffer` ?
>>
>>
>> kill-buffer is an interactive built-in function in ‘C source code’.
>
> Oops, sorry, it is indeed not possible to edebug C code. I don't
> suppose you've built your emacs with debug info so you could step with
> gdb?
It's built by Fedora (RedHat). I have debugging info but I belive
the emacs binary might be stripped, if that matters.
>
> Do you know how to reproduce this situation starting from 'emacs -Q',
> or is it a one-off fluke?
I dont know how to reproduce this with or without 'emacs -Q' but
it has happened to me periodically so I decided to finally
report it
I'll leave the sessuon around as long as I can.
I hope someone can help me to debug it.
Thanks.
This bug report was last modified 7 years and 204 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.