unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Reingruber, Richard" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "53348@debbugs.gnu.org" <53348@debbugs.gnu.org>
Subject: bug#53348: 27.2; Crash in mark_object
Date: Tue, 18 Jan 2022 17:07:53 +0000	[thread overview]
Message-ID: <E36FC338-E030-47B6-968D-E90E4073B7E0@sap.com> (raw)
In-Reply-To: <83bl09ugsf.fsf@gnu.org>

Hi Eli,

Thanks for looking at the issue!

The issue occurred today on another macbook which is x86_64 not arm64. OS and emacs versions are the same.

    > Looks like C stack overflow, or at least a possibility of it (you
    > didn't show all of the backtrace levels, so it's hard to be sure).

Yes, could be stack overflow. Is emacs' gc recursive? Will it crash if there is
a long enough list?

    > Can you configure your environment, or rebuild Emacs, so that the
    > amount of stack space available to it is larger?

Sure. I will try to configure my environment for larger stacks.

Thanks, Richard.

On 18.01.22, 17:53, "Eli Zaretskii" <eliz@gnu.org> wrote:

    > Date: Tue, 18 Jan 2022 08:35:10 +0000
    > From:  "Reingruber, Richard" via "Bug reports for GNU Emacs,
    >  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
    > 
    > I've got a new Apple M1 Pro macbook. I'm experiencing crashes with Emacs 27.2 which I installed using homebrew.
    > 
    > The information below was generated after I restarted Emacs following a crash.
    > 
    > I added the crash report from macos because I could not find a report from emacs.
    > 
    > Looks like a GC crash in mark_object.
    > 
    > Unfortunately I cannot reproduce the crash. This is the first crash report I
    > got. Normally Emacs just hangs. I sampled the process using macos activity
    > monitor and found a similar stack as in the crash.

    Looks like C stack overflow, or at least a possibility of it (you
    didn't show all of the backtrace levels, so it's hard to be sure).

    Can you configure your environment, or rebuild Emacs, so that the
    amount of stack space available to it is larger?


  reply	other threads:[~2022-01-18 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  8:35 bug#53348: 27.2; Crash in mark_object Reingruber, Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-18 16:53 ` Eli Zaretskii
2022-01-18 17:07   ` Reingruber, Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-18 17:49     ` Eli Zaretskii
2022-01-21 10:34       ` Lars Ingebrigtsen
2022-01-21 10:36         ` 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

  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=E36FC338-E030-47B6-968D-E90E4073B7E0@sap.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53348@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=richard.reingruber@sap.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).