unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp <p.stephani2@gmail.com>
To: Victor Tsaran <vtsaran@gmail.com>
Cc: 47378@debbugs.gnu.org
Subject: bug#47378: Emacs 27.1 binary Mac OS build crashes on Big Sur (11.x)
Date: Fri, 26 Mar 2021 18:56:04 +0100	[thread overview]
Message-ID: <C1D5C69D-6C42-4C0B-8209-EC0CB15BA2F8@gmail.com> (raw)
In-Reply-To: <CABUWEtdyQiGe7PjQaHv-ScN2kdx+ZHN5XX-zxd28+NzMCUnAsg@mail.gmail.com>



> Am 25.03.2021 um 06:36 schrieb Victor Tsaran <vtsaran@gmail.com>:
> 
> Hi.
> I apologize for not submitting this using Emacs's bug reporting system, but I d not use Emacs for my emailing needs, thus do not have the right setup for doing this.
> I am attaching the full crash log from Mac OS generated by the system and hope it will be helpful in diagnosing the problem.
> More background information below.
> 
> 1. I am using the clean Mac OS build of Emacs 27.1 from the Cask repository of Homebrew.
> 2. The build runs without any issues on Mac OS Catalina (10.15) using exact same packages and exact same configuration.
> 3. Emacs seems to abort with memory allocation errors, see the crash thread.

Looks like a double-free in draw_glyphs?  But that function is massive, so without further instrumentation it might be difficult to pin down the exact problem.
Could you try compiling with debugging symbols and then generating a stack trace using GDB or LLDB?  Another option would be to compile with address sanitization enabled.




  parent reply	other threads:[~2021-03-26 17:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  5:36 bug#47378: Emacs 27.1 binary Mac OS build crashes on Big Sur (11.x) Victor Tsaran
2021-03-26 17:33 ` Alan Third
2021-03-26 17:56 ` Philipp [this message]
2021-03-26 18:46   ` Eli Zaretskii
2021-04-17 19:05     ` Victor Tsaran
2022-06-27  8:25       ` Lars Ingebrigtsen
2021-10-21  4:45 ` Carlos Pita
     [not found] <18370489.1.1656382275637@localhost>
2022-06-28 11:56 ` Lars Ingebrigtsen
2022-06-28 16:58   ` Victor Tsaran

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=C1D5C69D-6C42-4C0B-8209-EC0CB15BA2F8@gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=47378@debbugs.gnu.org \
    --cc=vtsaran@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).