From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 48711@debbugs.gnu.org
Subject: bug#48711: Crashes in lisp_string_width
Date: Fri, 28 May 2021 10:11:35 +0300 [thread overview]
Message-ID: <83a6of8h94.fsf@gnu.org> (raw)
In-Reply-To: <87bl8vz7lu.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 28 May 2021 09:37:49 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Fri, 28 May 2021 09:37:49 +0300
>
> Yesterday's changes in lisp_string_width cause crashes:
>
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> composition_gstring_width (gstring=<optimized out>, from=1, from@entry=0, to=12, metrics=metrics@entry=0x0) at composite.c:777
> 777 if (NILP (LGLYPH_ADJUSTMENT (*glyph)))
> (gdb) bt
> #0 composition_gstring_width (gstring=<optimized out>, from=1, from@entry=0, to=12, metrics=metrics@entry=0x0) at composite.c:777
> #1 0x0000555555642ff7 in lisp_string_width (string=string@entry=XIL(0x555557825e54), from=from@entry=0, to=to@entry=1, precision=precision@entry=-1, nchars=nchars@entry=0x7fffffff4850, nbytes=nbytes@entry=0x7fffffff4858) at lisp.h:1644
> #2 0x000055555570c46e in styled_format (nargs=<optimized out>, args=<optimized out>, message=<optimized out>) at editfns.c:3392
> #3 0x0000555555716690 in Ffuncall (nargs=4, args=args@entry=0x7fffffffa060) at lisp.h:2093
Thanks, but I need a recipe to reproduce this, and/or at least some
idea about which variables cause the problem. The backtrace you show
is from an optimized build where the values of the relevant variables
are all "optimized out". That doesn't give me much to work with, and
there are no other experts on composite.c on board to help. So I need
all the help you can provide to fix this.
TIA
next prev parent reply other threads:[~2021-05-28 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 6:37 bug#48711: Crashes in lisp_string_width Juri Linkov
2021-05-28 7:11 ` Eli Zaretskii [this message]
2021-05-28 7:29 ` Eli Zaretskii
2021-05-28 8:39 ` Juri Linkov
2021-05-28 11:06 ` Eli Zaretskii
2021-05-28 18:32 ` Juri Linkov
2021-05-28 19:03 ` Eli Zaretskii
2021-05-29 21:38 ` Juri Linkov
2021-05-30 6:33 ` Eli Zaretskii
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=83a6of8h94.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48711@debbugs.gnu.org \
--cc=juri@linkov.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.