From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 34256@debbugs.gnu.org
Subject: bug#34256: 27.0.50; Crash on draw_glyphs()
Date: Wed, 30 Jan 2019 18:51:32 +0200 [thread overview]
Message-ID: <83k1im142z.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY0jP3UPRWOWADFYsDB4G6wd-C_28S7+2uVbN793=TZVSA@mail.gmail.com> (message from Kaushal Modi on Wed, 30 Jan 2019 11:35:32 -0500)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Wed, 30 Jan 2019 11:35:32 -0500
> Cc: 34256@debbugs.gnu.org
>
> Understood. I built that emacs with -O2 and without " --enable-checking='yes,glyphs'
> --enable-check-lisp-object-type" as it's my daily driver version.
I recommend always using these options when building the master
branch.
> I'll work on getting a recipe.
Thanks.
> Why isn't there a -g3 in the compiler switches? AFAIK, the default
> configuration supplies it.
>
> Yes, I did not add that switch; I do that in my debug builds.
Well, please always use that when you build the master branch. It's
potentially buggy code, so we need every possible piece of supporting
information to identify and solve bugs reported b y users.
> This was built using the latest master (i.e. with pdumper and no harfbuzz).
Makes sense. In that case, it is even more important to find the
reason for this, as there aren't supposed to be display-related
changes on master, so stuff like x_draw_glyph_string isn't supposed to
get in trouble.
Thanks.
next prev parent reply other threads:[~2019-01-30 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:30 bug#34256: 27.0.50; Crash on draw_glyphs() Kaushal Modi
2019-01-30 16:16 ` Eli Zaretskii
2019-01-30 16:35 ` Kaushal Modi
2019-01-30 16:51 ` Eli Zaretskii [this message]
2019-01-30 18:22 ` Kaushal Modi
2019-01-30 18:55 ` Eli Zaretskii
2019-01-30 20:54 ` Kaushal Modi
2019-01-31 14:02 ` Eli Zaretskii
2019-01-31 15:50 ` Kaushal Modi
2019-01-31 16:52 ` Eli Zaretskii
2019-01-31 17:02 ` Kaushal Modi
2019-01-31 17:05 ` Kaushal Modi
2019-01-31 20:26 ` Eli Zaretskii
2019-02-01 3:15 ` Kaushal Modi
2019-02-01 3:25 ` Kaushal Modi
2019-02-01 8:41 ` Eli Zaretskii
2019-02-04 16:03 ` Kaushal Modi
2019-02-04 17:50 ` 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
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=83k1im142z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34256@debbugs.gnu.org \
--cc=kaushal.modi@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).