unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: "Eli Zaretskii" <eliz@gnu.org>,
	"Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 56808@debbugs.gnu.org
Subject: bug#56808: 29.0.50; Elusive display problem on macOS
Date: Fri, 29 Jul 2022 15:17:54 +0200	[thread overview]
Message-ID: <ae0b02553e1ef67246dd8858e5a97704@condition-alpha.com> (raw)
In-Reply-To: <83r125ai2n.fsf@gnu.org>

Hello Eli,

I'm on a Mac, too, and can confirm Gerd's observations.

Eli Zaretskii <eliz@gnu.org> writes:

> [...]
> Are there any :align-to display properties involved in this?
> ("C-x =" could help you find out.)

I've done "C-u C-x =" across different locations in the indentation
until my fingers started aching, but no traces of :align-to display
properties, or anything else that seemed suspicious to me. It always
showed the expected font choice and size, i.e. all glyphs were reported
to be of the same size.

> Can you run this under a debugger and show the display elements in the
> offending glyph_row?  The easiest way of doing that with GDB is like
> this:
> [...]

Under lldb, most things show up as opaque Lisp_Object, i.e. can't drill
any deeper into those. I hence fail to figure out which buffer I'm
looking at when the breakpoint in set_cursor_from_row triggers. Lldb
does seem to find type information about the glyph_row though. Anything
in the row I should be looking out for?

FWIW, here are a few examples of gdb vs. lldb commands:
https://developer.apple.com/library/archive/documentation/IDEs/Conceptual/gdb_to_lldb_transition_guide/document/lldb-command-examples.html#//apple_ref/doc/uid/TP40012917-CH3-SW1



Hoping to have helped,

  --alexander





  parent reply	other threads:[~2022-07-29 13:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  5:09 bug#56808: 29.0.50; Elusive display problem on macOS Gerd Möllmann
2022-07-28  6:04 ` Eli Zaretskii
2022-07-28  7:37   ` Gerd Möllmann
2022-07-28  8:01     ` Eli Zaretskii
2022-07-28  9:18       ` Gerd Möllmann
2022-07-28 11:31         ` Gerd Möllmann
2022-07-28 12:07           ` Gerd Möllmann
2022-07-28 13:03             ` Gerd Möllmann
2022-07-28 13:37             ` Eli Zaretskii
2022-07-28 15:04               ` Gerd Möllmann
2022-07-28 15:12                 ` Eli Zaretskii
2022-07-28 17:13                   ` Gerd Möllmann
2022-07-29 12:32                     ` Gerd Möllmann
2022-07-29 13:52                       ` YAMAMOTO Mitsuharu
2022-07-29 14:32                         ` Gerd Möllmann
2022-07-30  7:49                           ` YAMAMOTO Mitsuharu
2022-07-30  7:54                             ` Gerd Möllmann
2022-07-30  8:13                             ` Eli Zaretskii
2022-07-30  8:28                               ` YAMAMOTO Mitsuharu
2022-07-29 13:17   ` Alexander Adolf [this message]
2022-07-29 14:18     ` 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=ae0b02553e1ef67246dd8858e5a97704@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=56808@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.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).