From: Jason May via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 47139@debbugs.gnu.org
Subject: bug#47139: macOS Emacs 27.1 - planarGetBytes warning
Date: Sat, 20 Mar 2021 10:44:05 -0700 [thread overview]
Message-ID: <10c6cd1160f9e3000d56f3b7a6632e194a752cb7@hey.com> (raw)
In-Reply-To: <c37ab47c072b3444364f2a73ffc66908daf5015b@hey.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Both the emacsformacosx.com versions and the homebrew cask version
output the same message to stderr. These are not identical versions
(executable size is different, unclear what is included or not included
in each) but both claim to be 27.1.
I'm also convinced that this message is coming from the OS/GUI, but
planarGetBytes is not documented anywhere so I wonder if it some sort of
low-level constructed method call.
I've seen reports of other users seeing similar errors over the last
several years, but the precise message contents don't always match.
"count (N) is less than bytesPerRow (M)" where N & M are different.
I'll try a full build from source and see if it still occurs. If I could
find a way to generate a stacktrace when this happens then I might be
able to track it back to the particular emacs event. Currently I can't
find any correlation with my usage.
[-- Attachment #2: Type: text/html, Size: 3307 bytes --]
next prev parent reply other threads:[~2021-03-20 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 18:17 bug#47139: emacs 27.1 on MacOS Big Sur - "planarGetBytes" errors on console Jason May
2021-03-15 21:48 ` Alan Third
2021-03-20 17:44 ` Jason May via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-24 13:14 ` Lars Ingebrigtsen
2022-06-26 17:03 ` Jason May via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-26 17:05 ` Lars Ingebrigtsen
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=10c6cd1160f9e3000d56f3b7a6632e194a752cb7@hey.com \
--to=bug-gnu-emacs@gnu.org \
--cc=47139@debbugs.gnu.org \
--cc=jason.may@hey.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 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).