From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73838@debbugs.gnu.org
Subject: bug#73838: 31.0.50; Problems in note_mouse_highlight if -nw
Date: Thu, 17 Oct 2024 14:39:58 +0200 [thread overview]
Message-ID: <m2sesuq4wx.fsf@gmail.com> (raw)
In-Reply-To: <865xprovli.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Oct 2024 13:46:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: 73838@debbugs.gnu.org
>> Date: Thu, 17 Oct 2024 09:03:13 +0200
>>
>> The immediate problem I'm facing is with tty child frames and
>> xterm-mouse: I'm opening a buffer selection child frame (consult-buffer)
>> and choose a candidate with a mouse click. The candidates are
>> mouse-highlighted. Result is eventually an endless loop in
>> process_mark_stack in the non-MPS GC. (Not using the mouse works just
>> fine.)
>
> If you can show the details of that, i.e. step through the loop one
> time until it gets to the same point, maybe someone could have an
> idea.
It's probably something pretty strange:
I built with ASAN, no MPS but my workaround for the hightlighting, and
get an error: GC marks char-code-property-alist (staticpro), and hits a
char-table object that is somehow broken. pdumper-object-p says yes for
it, but when checking the mark bit of that char-table with
pdumper_marked_p_impl, ASAN complains about an access outside of the
bitset being used for the pdumper mark bits.
(Not sure if that's already the loop I see without ASAN.)
Didn't get further than that today. LLDB decided to crash as well at
some point.
I'm a bit out of ideas how to find out what's up with that char-table.
Maybe I'll wait a bit until I have an idea how I could find that out.
next prev parent reply other threads:[~2024-10-17 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 10:47 bug#73838: 31.0.50; Problems in note_mouse_highlight if -nw Gerd Möllmann
2024-10-16 14:19 ` Gerd Möllmann
2024-10-16 15:38 ` Eli Zaretskii
2024-10-16 16:56 ` Gerd Möllmann
2024-10-16 18:30 ` Eli Zaretskii
2024-10-16 19:03 ` Gerd Möllmann
2024-10-17 4:06 ` Eli Zaretskii
2024-10-17 5:07 ` Gerd Möllmann
2024-10-17 5:48 ` Eli Zaretskii
2024-10-17 7:03 ` Gerd Möllmann
2024-10-17 10:44 ` Eli Zaretskii
2024-10-17 12:12 ` Gerd Möllmann
2024-10-17 10:46 ` Eli Zaretskii
2024-10-17 12:39 ` Gerd Möllmann [this message]
2024-10-19 3:50 ` Gerd Möllmann
2024-10-19 8:00 ` Gerd Möllmann
2024-10-16 15:27 ` Eli Zaretskii
2024-10-16 16:41 ` Gerd Möllmann
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=m2sesuq4wx.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=73838@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).