From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 33345@debbugs.gnu.org
Subject: bug#33345: 27.0.50; Abort in bidi_cache_iterator_state
Date: Mon, 12 Nov 2018 18:08:33 +0200 [thread overview]
Message-ID: <8336s69t32.fsf@gnu.org> (raw)
In-Reply-To: <jwvefbqct9o.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Mon, 12 Nov 2018 08:43:34 -0500)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: 33345@debbugs.gnu.org
> Date: Mon, 12 Nov 2018 08:43:34 -0500
>
> OK, I've managed to do that. The resulting file is attached.
Thanks. Doesn't crash here :-( Tried on MS-Windows and on GNU/Linux.
> But it doesn't look like a bug in bidi, after all:
> - `emacs ~/tmp/foobug.txt`
> crashes right away
> - `emacs --eval '(setq bidi-display-reordering nil)' ~/tmp/foobug.txt`
> crashes right away as well!
The last one should have been
`emacs --eval '(setq-default bidi-display-reordering nil)' ~/tmp/foobug.txt`
> - `emacs -Q ~/tmp/foobug.txt`
> does not crash
> - `emacs --eval '(garbage-collect)' ~/tmp/foobug.txt`
> does not crash either!
So we are looking at some strange memory-allocation bug or somesuch?
> Also, when I tried to reproduce it yesterday (in order to produce the
> file), I was on another machine and that one did not crash either.
> The two machines are both running Debian but have various important
> differences: 64bit-vs-32bit and stable-vs-testing.
>
> So, I wouldn't be surprised at all if noone else manages to reproduce
> the crash.
Can you try Emacs 26 on the same system where Emacs 27 crashes? And
what about unoptimized build of Emacs 27 -- does it crash as well?
Finally, do you have local changes, or is this stock master HEAD?
next prev parent reply other threads:[~2018-11-12 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 15:03 bug#33345: 27.0.50; Abort in bidi_cache_iterator_state Stefan Monnier
2018-11-11 16:03 ` Eli Zaretskii
2018-11-12 13:43 ` Stefan Monnier
2018-11-12 16:08 ` Eli Zaretskii [this message]
2018-11-12 17:50 ` Eli Zaretskii
2018-11-13 18:05 ` Eli Zaretskii
2018-11-13 18:28 ` Stefan Monnier
2020-11-25 9:53 ` Stefan Kangas
2020-11-25 14:26 ` Stefan Monnier
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=8336s69t32.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33345@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.