From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: luangruo@yahoo.com, 56553@debbugs.gnu.org
Subject: bug#56553: 29.0.50; ASAN error with fringe bitmaps on NS
Date: Fri, 15 Jul 2022 13:37:01 +0300 [thread overview]
Message-ID: <83mtdaslv6.fsf@gnu.org> (raw)
In-Reply-To: <FC63D0B4-DDA2-4F29-9B0B-A4ED78DF8D8F@gmail.com> (message from Gerd Möllmann on Fri, 15 Jul 2022 11:14:02 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Fri, 15 Jul 2022 11:14:02 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 56553@debbugs.gnu.org
>
>
> > On 2022-07-15,, at 10:23 , Po Lu <luangruo@yahoo.com> wrote:
>
> > Yes, you're right here. I think that code does want to access the
> > individual bytes.
>
> Interestingly, just doing
>
> const char *bitmap_bytes = (const char *) bits;
> bool bit = bitmap_bytes[byte] & (0x80 >> x % 8);
>
> here results in garbage fringe bitmaps beign displayed. I'm stumped.
Is the machine little-endian or big-endian?
next prev parent reply other threads:[~2022-07-15 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 13:03 bug#56553: 29.0.50; ASAN error with fringe bitmaps on NS Gerd Möllmann
2022-07-14 13:56 ` Eli Zaretskii
2022-07-14 14:18 ` Gerd Möllmann
2022-07-14 14:34 ` Gerd Möllmann
2022-07-14 16:55 ` Eli Zaretskii
2022-07-14 18:25 ` Gerd Möllmann
2022-07-15 8:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 9:14 ` Gerd Möllmann
2022-07-15 10:37 ` Eli Zaretskii [this message]
2022-07-15 13:55 ` Gerd Möllmann
2022-07-15 13:57 ` Robert Pluim
2022-07-15 14:26 ` Eli Zaretskii
2022-07-15 14:46 ` Andreas Schwab
2022-07-15 15:10 ` Gerd Möllmann
2022-07-15 15:16 ` Gerd Möllmann
2022-07-16 7:16 ` Gerd Möllmann
2022-07-15 15:32 ` Andreas Schwab
2022-07-15 10:35 ` Eli Zaretskii
2022-07-15 10:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mtdaslv6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56553@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.com \
/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.