From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#56553: 29.0.50; ASAN error with fringe bitmaps on NS Date: Fri, 15 Jul 2022 15:55:40 +0200 Message-ID: <12E0397A-F443-4A1F-88F2-D3C8EA6D279C@gmail.com> References: <83cze7u7b7.fsf@gnu.org> <8569ECF9-6D19-4DCB-854C-2755D182F8AF@gmail.com> <8335f3tz02.fsf@gnu.org> <87cze6okcy.fsf@yahoo.com> <83mtdaslv6.fsf@gnu.org> Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34034"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , 56553@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 15 15:56:12 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oCLng-0008Y2-4I for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 15 Jul 2022 15:56:12 +0200 Original-Received: from localhost ([::1]:45618 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oCLnd-0007IS-Sg for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 15 Jul 2022 09:56:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55784) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oCLnW-0007IH-Bp for bug-gnu-emacs@gnu.org; Fri, 15 Jul 2022 09:56:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44090) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oCLnW-000306-2v for bug-gnu-emacs@gnu.org; Fri, 15 Jul 2022 09:56:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oCLnV-0002Fm-W0 for bug-gnu-emacs@gnu.org; Fri, 15 Jul 2022 09:56:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 15 Jul 2022 13:56:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56553 X-GNU-PR-Package: emacs Original-Received: via spool by 56553-submit@debbugs.gnu.org id=B56553.16578933508370 (code B ref 56553); Fri, 15 Jul 2022 13:56:01 +0000 Original-Received: (at 56553) by debbugs.gnu.org; 15 Jul 2022 13:55:50 +0000 Original-Received: from localhost ([127.0.0.1]:41564 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oCLnJ-0002At-Sz for submit@debbugs.gnu.org; Fri, 15 Jul 2022 09:55:50 -0400 Original-Received: from mail-ej1-f45.google.com ([209.85.218.45]:33623) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oCLnH-00024g-Jv for 56553@debbugs.gnu.org; Fri, 15 Jul 2022 09:55:48 -0400 Original-Received: by mail-ej1-f45.google.com with SMTP id va17so9188933ejb.0 for <56553@debbugs.gnu.org>; Fri, 15 Jul 2022 06:55:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=T+9JnB/MaHzM20viT3d+vTHvJWnZaPmd9Fns6WNvjU4=; b=gqxDRrG29b4ahG15ZnN8Ov/GZu7T+Wa31QWtaT1BWDspe/qamcuqUgtNiAxQGTS2xk BDurPPH90f55Rcs2E8qP5NjSO5ZSapYiwKHqu36or+4H9j4ZCIAcf5Nh7fVj2kTkF5IL bEmE3ckv893JL1yAWaBbvaqtt0s6/h/Xfof4rfYoLyfDIaAAba5udbzXMRxC+msinmaY +g1TVLtF/br2x2owXOkukVUq5aU6elROnFmL7WAxncY4Blib9zP+7GOgKEN8CB3+Sl7P fknQCAZ8btcH6XO/BQKdGIGP8ZHD2Pa/Pg8HW+ptxB3RWC239+XNZ5KEv/923hWxCKei 7NKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=T+9JnB/MaHzM20viT3d+vTHvJWnZaPmd9Fns6WNvjU4=; b=3jD1+Gdw7rHNyG7CACO7cxoGDZ7KKMeFpEQ9Yoz34nroDDCHICmVQ/65GVhIPSNMSG b8QzQqDKGjAk9Sfdcxw4I14Svt1O/Gfrj/DsafTIq0oiGSe5dSn7KAH5skKATb5coc8P F/lNkG+xc5kpM6z+JebKEfRbIwTVtatDfwNo06KP8VLAUQSbeseazlytgXWdGVNJzV5e wAeL4+3MiYJDXQpCga2hNv/8USzXKxgFgrFBmBclQVNtWlBXIIXR2blHHCykhD3R4197 naZG+TFShm2dxdx4+mE4LvV5DeC1Y6qzqJTkqBNN3KZ9+Qa60h1anP+Owf5fGjjte0vw H+8w== X-Gm-Message-State: AJIora+9Sbnaklz8AUHhszNYA/nv1eecus64n7na/LbsxXyP+YUNHiWI EKPHk13H9A+N5bvoLlSgnjs= X-Google-Smtp-Source: AGRyM1vIv4sMBUhx3GYwpKPOhzvE6rh2d0LhQ/YaazN8IXorqAAufmWKse6C4DOKc49zSZNC2vZJXg== X-Received: by 2002:a17:907:28c9:b0:72b:7165:20c2 with SMTP id en9-20020a17090728c900b0072b716520c2mr13610695ejc.120.1657893341565; Fri, 15 Jul 2022 06:55:41 -0700 (PDT) Original-Received: from smtpclient.apple (pd9e368e5.dip0.t-ipconnect.de. [217.227.104.229]) by smtp.gmail.com with ESMTPSA id bo15-20020a0564020b2f00b0043a896048basm2935906edb.85.2022.07.15.06.55.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jul 2022 06:55:41 -0700 (PDT) In-Reply-To: <83mtdaslv6.fsf@gnu.org> X-Mailer: Apple Mail (2.3696.100.31) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:237101 Archived-At: > On 2022-07-15,, at 12:37 , Eli Zaretskii wrote: >=20 >> From: Gerd M=C3=B6llmann >> Date: Fri, 15 Jul 2022 11:14:02 +0200 >> Cc: Eli Zaretskii , >> 56553@debbugs.gnu.org >>=20 >>=20 >>> On 2022-07-15,, at 10:23 , Po Lu wrote: >>=20 >>> Yes, you're right here. I think that code does want to access the >>> individual bytes. >>=20 >> Interestingly, just doing >>=20 >> const char *bitmap_bytes =3D (const char *) bits; >> bool bit =3D bitmap_bytes[byte] & (0x80 >> x % 8); >>=20 >> here results in garbage fringe bitmaps beign displayed. I'm stumped. >=20 > Is the machine little-endian or big-endian? Good question! I think it's little-endian, but I'm not 100% sure.=20