From: Stefan Kangas <stefan@marxist.se>
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: Wed, 25 Nov 2020 01:53:21 -0800 [thread overview]
Message-ID: <CADwFkmkAWGgDJ1AxM4F1zt1gx8JCib=dC9W7R-1Q=bREzAv4=g@mail.gmail.com> (raw)
In-Reply-To: <jwv4lckbzt5.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 13 Nov 2018 13:28:23 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> But this means that the cache is empty, and we can never scan back
>> (scan_dir = -1) when the cache is empty. So something very strange
>> happened there.
>
> I think it's a case of memory corruption and doesn't really have much to
> do with bidi code. But I'm not progressing very fast: it's somewhat
> deterministic but it is influenced by elements I'm not aware of, so it's
> pretty nasty.
>
>> Instead of me asking you gobs of questions, perhaps you could give me
>> an ssh login on that system, and arrange for a GDB session which
>> already hit the call to emacs_abort to be in a state where I can
>> switch to it after logging in (with 'screen' or 'tmux', I think).
>> Then I could look around and see if I find out some clues.
>
> It's a machine that's not reachable from the internet and is off most of
> the time. I haven't yet managed to reproduce it on another machine.
> I'll let you know when I'm making progress,
This bug was reported 2 years ago, so just pinging to see if it's still
relevant. Thanks.
next prev parent reply other threads:[~2020-11-25 9:53 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
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 [this message]
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='CADwFkmkAWGgDJ1AxM4F1zt1gx8JCib=dC9W7R-1Q=bREzAv4=g@mail.gmail.com' \
--to=stefan@marxist.se \
--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.