From: Eli Zaretskii <eliz@gnu.org>
To: Yagnesh Raghava Yakkala <hi@yagnesh.org>
Cc: 18815@debbugs.gnu.org
Subject: bug#18815: 25.0.50; emacs crash
Date: Mon, 27 Oct 2014 21:10:28 +0200 [thread overview]
Message-ID: <83r3xt2usb.fsf@gnu.org> (raw)
In-Reply-To: <8738a9mkbv.fsf@sealion.lowtem.hokudai.ac.jp>
> From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
> Cc: 18815@debbugs.gnu.org
> Date: Tue, 28 Oct 2014 03:36:04 +0900
>
> > This string comes from column-number-mode. But if I invoke
> > column-number-mode, I still cannot reproduce the problem, so there's
> > something else at work here. Can you describe what you do to
> > reproduce the crash?
>
> Crashes on different tasks. Using magit, some times C-x C-f. But one reliable
> way was, selecting a url in a buffer with M-x ffap and RET.
So, if you start Emacs, visit a file with URLs, then "M-x ffap RET",
you get a crash, just like that? Or do you need Emacs to run for some
time before it crashes with ffap?
> (gdb) xstring
> $3 = (struct Lisp_String *) 0x10d7b30
> " (%l,%c)"
> (gdb) frame 3
> #3 0x000000000050f332 in bidi_resolve_neutral (bidi_it=0x7fffffff36a8) at bidi.c:2852
> (gdb) p bidi_it->charpos
> $4 = 7
> (gdb) p bidi_it->next_for_neutral
> $5 = {
> charpos = 7,
> type = STRONG_L,
> orig_type = UNKNOWN_BT
> }
> (gdb) p bidi_it->prev_for_neutral
> $6 = {
> charpos = 6,
> type = STRONG_L,
> orig_type = STRONG_L
> }
> (gdb) p bidi_it->bracket_pairing_pos
> $7 = -1
> (gdb) p bidi_it->bracket_enclosed_type
> $8 = UNKNOWN_BT
> (gdb) p bidi_cache_idx
> $9 = 3
> (gdb) p bidi_cache_start
> $10 = 2
This means your mode line has some non-trivial setup, and it is most
probably that setup which triggers the problem. Can you please tell
which modes of those you invoke affect the mode line? I want to be
able to reproduce this problem on my system, because otherwise I don't
see how I can solve this just by asking you to look around in the
crashed session.
Thanks.
next prev parent reply other threads:[~2014-10-27 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:41 bug#18815: 25.0.50; emacs crash Yagnesh Raghava Yakkala
2014-10-24 12:55 ` Eli Zaretskii
2014-10-24 13:21 ` Eli Zaretskii
2014-10-24 17:36 ` Yagnesh Raghava Yakkala
2014-10-24 19:24 ` Eli Zaretskii
2014-10-25 3:43 ` Yagnesh Raghava Yakkala
2014-10-25 6:45 ` Eli Zaretskii
2014-10-26 5:29 ` Yagnesh Raghava Yakkala
2014-10-26 15:49 ` Eli Zaretskii
2014-10-26 22:57 ` Yagnesh Raghava Yakkala
2014-10-27 17:18 ` Eli Zaretskii
2014-10-27 18:36 ` Yagnesh Raghava Yakkala
2014-10-27 19:10 ` Eli Zaretskii [this message]
2014-10-28 3:14 ` Yagnesh Raghava Yakkala
2014-10-28 3:38 ` Eli Zaretskii
2014-10-28 4:42 ` Yagnesh Raghava Yakkala
2019-10-13 1:30 ` Lars Ingebrigtsen
2019-10-13 7:11 ` 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=83r3xt2usb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18815@debbugs.gnu.org \
--cc=hi@yagnesh.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).