From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: 25883@debbugs.gnu.org
Subject: bug#25883: 25.2; Frequent, but not reproducible, crash on startup
Date: Sun, 26 Feb 2017 22:07:14 +0200 [thread overview]
Message-ID: <83zih8pvgt.fsf@gnu.org> (raw)
In-Reply-To: <m2a898wxau.fsf@newartisans.com> (message from John Wiegley on Sun, 26 Feb 2017 11:45:45 -0800)
> From: John Wiegley <jwiegley@gmail.com>
> Cc: bug-gnu-emacs@gnu.org
> Date: Sun, 26 Feb 2017 11:45:45 -0800
>
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I am not familiar enough with ERC support in Emacs -- is it possible that
> > Emacs tries to display some partial byte stream that includes incomplete
> > characters, i.e. the byte sequence for some character(s) is incomplete?
>
> Not only possible, but likely. What happens is this:
>
> 1. Emacs starts up
> 2. ERC begins initializing
> 3. ERC logins in to ZNC
> 4. ZNC starts playing black all the messages that came in since I last
> exited Emacs.
> 5. Emacs sometimes survives this, sometimes crashes.
>
> So it's quite possible that a "past message" ZNC is playing back contains a
> partial byte sequence.
It's important to have the text of the buffer at the point of crash.
I could tell you how to do that with GDB, but I don't know how with
other debuggers.
Does ERC display include overlays or display strings or images? Or
maybe (space . PROPS) display properties? Or any other kind of
non-buffer text?
next prev parent reply other threads:[~2017-02-26 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 19:14 bug#25883: 25.2; Frequent, but not reproducible, crash on startup John Wiegley
2017-02-26 19:34 ` Eli Zaretskii
2017-02-26 19:45 ` John Wiegley
2017-02-26 20:07 ` Eli Zaretskii [this message]
2017-02-26 20:37 ` John Wiegley
2017-02-26 20:44 ` Eli Zaretskii
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=83zih8pvgt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25883@debbugs.gnu.org \
--cc=jwiegley@gmail.com \
/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.