unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34256@debbugs.gnu.org
Subject: bug#34256: 27.0.50; Crash on draw_glyphs()
Date: Wed, 30 Jan 2019 11:35:32 -0500	[thread overview]
Message-ID: <CAFyQvY0jP3UPRWOWADFYsDB4G6wd-C_28S7+2uVbN793=TZVSA@mail.gmail.com> (raw)
In-Reply-To: <83pnse15pb.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

On Wed, Jan 30, 2019 at 11:16 AM Eli Zaretskii <eliz@gnu.org> wrote:

>
> Do you strip Emacs when you install it?  If so, please don't, because
> when you strip the debugging symbols, you lose the capability of
> giving us any useful information about the crash.
>

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.



> If you can reproduce this problem, please post the recipe; otherwise I
> don't see how this could be of any use.  Too bad.
>

I'll work on getting a recipe.

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.


>   Did you specify CFLAGS at configure time?
> If so, please add -g3 to the switches, and I suggest to use -Og,
> not -O2, for better debuggability.
>

Will do.

Did you merge the harfbuzz branch with master, so there's no pdumper
> in your build?


Actually, sorry for that confusion. I realized that I had the
--with-harfbuff switch since when I tried the harfbuff branch, but forgot
to remove that from my build script.


> If not, why do I see CANNOT_DUMP in the list of
> features?
>

This was built using the latest master (i.e. with pdumper and no harfbuzz).

I'll try to get a recipe.

[-- Attachment #2: Type: text/html, Size: 2629 bytes --]

  reply	other threads:[~2019-01-30 16:35 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 [this message]
2019-01-30 16:51     ` Eli Zaretskii
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='CAFyQvY0jP3UPRWOWADFYsDB4G6wd-C_28S7+2uVbN793=TZVSA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=34256@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).