unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: sds@gnu.org, 57751@debbugs.gnu.org
Subject: bug#57751: 29.0.50; crash in GC
Date: Thu, 15 Sep 2022 12:23:15 +0300	[thread overview]
Message-ID: <83o7vhyosc.fsf@gnu.org> (raw)
In-Reply-To: <m2fsgtdo63.fsf@Mini.fritz.box> (message from Gerd Möllmann on Thu, 15 Sep 2022 10:42:12 +0200)

> Cc: 57751@debbugs.gnu.org
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Thu, 15 Sep 2022 10:42:12 +0200
> 
> Save the following 2 lines as crash.el, which are what I could reduce my
> init file to:
> 
> (custom-set-variables
>  '(save-place-mode t))
> 
> Then start Emacs from the src directory like this:
> 
> lldb emacs
> run -Q  -l crash.el xdisp.c dispextern.h lisp.h nsterm.m xterm.c
> 
> When the Emacs GUI window appears, quickly grab its titlebar with the
> mouse and drag it up.  I usually need a few trials (< 10) to be
> quick enough, or what the reason might be.
> 
> Result:
> 
> Process 94346 stopped
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1705bfbb0)
>     frame #0: 0x0000000100145e18 emacs`process_mark_stack [inlined] symbol_marked_p(s=0x00000001705bfbb0) at alloc.c:4020:7 [opt]
>    4017	{
>    4018	  return pdumper_object_p (s)
>    4019	    ? pdumper_marked_p (s)
> -> 4020	    : s->u.s.gcmarkbit;
>    4021	}
>    4022	
>    4023	static void

I cannot reproduce this.  Maybe this is specific to macOS, or maybe
one needs to build with native-comp and/or with optimizations?





  parent reply	other threads:[~2022-09-15  9:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 14:37 bug#57751: 29.0.50; crash in GC Sam Steingold
2022-09-13  5:20 ` Gerd Möllmann
2022-09-13 14:51   ` Sam Steingold
2022-09-14  5:46     ` Gerd Möllmann
2022-09-14 18:36       ` Sam Steingold
2022-09-15  5:28         ` Gerd Möllmann
2022-09-15  8:42           ` Gerd Möllmann
2022-09-15  8:48             ` Gerd Möllmann
2022-09-15 10:01               ` Gerd Möllmann
2022-09-15 12:10                 ` Eli Zaretskii
2022-09-15 15:12                   ` Gerd Möllmann
2022-09-15 16:48                 ` Sam Steingold
2022-09-15 22:25                 ` Gregory Heytings
2022-09-15 22:41                   ` Sam Steingold
2022-09-15 22:42                   ` Sam Steingold
2022-09-15 23:17                     ` Gregory Heytings
2022-09-16  5:40                       ` Gerd Möllmann
2022-09-19 16:26                         ` Sam Steingold
2022-09-20  4:32                           ` Gerd Möllmann
2022-09-15  9:23             ` Eli Zaretskii [this message]
2022-09-15  9:37               ` Gerd Möllmann
2022-09-15 16:45             ` Sam Steingold
2022-09-15 16:35           ` Sam Steingold
2022-09-14 11:30     ` Gerd Möllmann
2022-09-14 11:32       ` Gerd Möllmann
2022-09-14 18:20       ` Sam Steingold
2022-09-15  4:49         ` Gerd Möllmann

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=83o7vhyosc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57751@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=sds@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).