From: Ken Raeburn <raeburn@permabit.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23013@debbugs.gnu.org
Subject: bug#23013: 25.0.92; assertion failure on marker outside text range in echo area
Date: Tue, 15 Mar 2016 17:16:33 -0400 [thread overview]
Message-ID: <CAJJWxE9_xUORoZ2Xy8iLkwdBXGaa6dQ6YUhJMvX2hP9RbVDMrQ@mail.gmail.com> (raw)
In-Reply-To: <8337rrbiuh.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Tue, Mar 15, 2016 at 4:13 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 15 Mar 2016 15:46:37 -0400
> > From: Ken Raeburn <raeburn@permabit.com>
> > Cc: 23013@debbugs.gnu.org
> >
> > And the buffer still has a name; killing the buffer sets the name to
> > nil.
>
> Emacs will promptly recreate the echo-area buffers if they are killed.
>
As I understand it, that'd be a new buffer, and the one pointed to by the
marker would still be dead (name=nil), wouldn't it?
And as I said, the first time I wasn't killing a buffer. After extracting
the recent keys from the earlier core file (we don't have a gdb macro for
this??), I've confirmed I was switching to an existing shell command output
buffer.
[-- Attachment #2: Type: text/html, Size: 1270 bytes --]
next prev parent reply other threads:[~2016-03-15 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 19:55 bug#23013: 25.0.92; assertion failure on marker outside text range in echo area Ken Raeburn
2016-03-15 19:00 ` Ken Raeburn
2016-03-15 19:14 ` Eli Zaretskii
2016-03-15 19:46 ` Ken Raeburn
2016-03-15 20:13 ` Eli Zaretskii
2016-03-15 21:16 ` Ken Raeburn [this message]
2016-03-16 15:32 ` Eli Zaretskii
2016-03-16 19:28 ` Ken Raeburn
2016-03-17 17:06 ` Eli Zaretskii
2016-04-07 22:32 ` Ken Raeburn
2016-04-08 7:38 ` Eli Zaretskii
2016-04-22 21:01 ` Ken Raeburn
2016-04-23 7:55 ` Eli Zaretskii
2020-08-12 3:33 ` Stefan Kangas
2020-09-14 21:23 ` Ken Raeburn
2020-09-15 7:35 ` Stefan Kangas
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=CAJJWxE9_xUORoZ2Xy8iLkwdBXGaa6dQ6YUhJMvX2hP9RbVDMrQ@mail.gmail.com \
--to=raeburn@permabit.com \
--cc=23013@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.