From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 22818@debbugs.gnu.org, josh@berdine.net
Subject: bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs
Date: Sat, 19 Nov 2016 17:09:06 +0200 [thread overview]
Message-ID: <83d1hrbj71.fsf@gnu.org> (raw)
In-Reply-To: <20161119145336.GA591@breton.holly.idiocy.org> (message from Alan Third on Sat, 19 Nov 2016 14:53:36 +0000)
> Date: Sat, 19 Nov 2016 14:53:36 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: josh@berdine.net, 22818@debbugs.gnu.org
>
> (gdb) p s->face.id
> $2 = 17
> (gdb) p lface_id_to_name[17]
> $3 = 31008
> (gdb) xsymbol(lface_id_to_name[17])
> $4 = (struct Lisp_Symbol *) 0x7ab8
> Cannot access memory at address 0x7ac0
>
> am I doing this wrong?
The last command should be simply "xsymbol". Those x* commands are
defined such that they always operate on the last result printed by
GDB.
Thanks.
next prev parent reply other threads:[~2016-11-19 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:41 bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Aaron S. Hawley
2016-05-18 20:07 ` Alan Third
2016-05-18 21:09 ` Aaron S. Hawley
2016-11-18 21:31 ` bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs Josh Berdine
2016-11-19 7:07 ` Eli Zaretskii
2016-11-19 10:07 ` Alan Third
2016-11-19 10:27 ` Eli Zaretskii
2016-11-19 11:18 ` Alan Third
2016-11-19 11:43 ` Eli Zaretskii
2016-11-19 14:53 ` Alan Third
2016-11-19 15:09 ` Eli Zaretskii [this message]
2016-11-19 15:51 ` Alan Third
2016-11-19 18:12 ` Eli Zaretskii
2016-11-19 19:05 ` Alan Third
2016-11-19 19:27 ` Eli Zaretskii
2016-11-19 19:38 ` Alan Third
2022-04-18 11:32 ` bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Lars Ingebrigtsen
2022-04-18 11:44 ` Aaron S. Hawley
2022-04-18 11:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d1hrbj71.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22818@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=josh@berdine.net \
/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.