From: Andy Moreton <andrewjmoreton@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23221-done@debbugs.gnu.org
Subject: bug#23221: 25.0.92; Crash in redisplay during isearch
Date: Tue, 5 Apr 2016 18:06:23 +0100 [thread overview]
Message-ID: <5703F08F.3020903@gmail.com> (raw)
In-Reply-To: <83fuv0m4fh.fsf@gnu.org>
On 05/04/2016 5:00 PM, Eli Zaretskii wrote:
>> Cc: 23221@debbugs.gnu.org
>> From: Andy Moreton <andrewjmoreton@gmail.com>
>> Date: Tue, 5 Apr 2016 16:42:59 +0100
>>
>> Feel free to close this, as I can't reproduce it, and I don't have the crashed
>> session open in gdb any more.
>
> Done. Next time something like this happen, please try at least to
> establish the values directly involved in the assertion violation,
> like the character and byte position in this case. (Did that a buffer
> include non-ASCII characters, btw?)
Sorry - I did intend to get a full backtrace, however MSYS2 gdb does not
support readline properly, so it is all too easy to get it confused :-(
The buffer was a listing of the Cygwin mailing list at gmane.org, so included
some non-ASCII characters in names, and some unicode box drawing chars in the
threading tree:
(setq gnus-sum-thread-tree-single-indent "□ " ; U+25A1
gnus-sum-thread-tree-false-root "▷ " ; U+25B7
gnus-sum-thread-tree-root "▶ " ; U+25B6
gnus-sum-thread-tree-vertical "│ " ; U+2502
gnus-sum-thread-tree-leaf-with-other "├─□ " ; U+251C U+2500 U+25A1
gnus-sum-thread-tree-single-leaf "╰─□ " ; U+2570 U+2500 U+25A1
gnus-sum-thread-tree-indent " ")
next prev parent reply other threads:[~2016-04-05 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 13:28 bug#23221: 25.0.92; Crash in redisplay during isearch Andy Moreton
2016-04-05 14:52 ` Eli Zaretskii
2016-04-05 15:09 ` Andy Moreton
2016-04-05 15:37 ` Eli Zaretskii
2016-04-05 15:42 ` Andy Moreton
2016-04-05 16:00 ` Eli Zaretskii
2016-04-05 17:06 ` Andy Moreton [this message]
2016-04-05 19:21 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5703F08F.3020903@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=23221-done@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).