all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mike Hamrick <mikeh@muppetlabs.com>
Cc: 38936@debbugs.gnu.org
Subject: bug#38936: 27.0.60; vector_marked_p: GC crash
Date: Fri, 30 Oct 2020 15:34:08 +0100	[thread overview]
Message-ID: <87lffng4v3.fsf@gnus.org> (raw)
In-Reply-To: <m136cuirsj.fsf@eidolon.muppetlabs.com> (Mike Hamrick's message of "Sat, 04 Jan 2020 18:02:52 -0800")

Mike Hamrick <mikeh@muppetlabs.com> writes:

> I've experienced a few crashes recently during GC, which makes it
> challenging to come up with steps to reproduce.  I did however manage
> to catch one in the debugger. Please find the attached stack trace and
> system information below.
>
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
>     frame #0: 0x0000000100222a28 Emacs`vector_marked_p(v=0x001dffffa21bfa11) at alloc.c:3726:10
>    3723         }

[...]

>   * frame #0: 0x0000000100222a28 Emacs`vector_marked_p(v=0x001dffffa21bfa11) at alloc.c:3726:10
>     frame #1: 0x0000000100226085 Emacs`vectorlike_marked_p(header=0x001dffffa21bfa11) at alloc.c:3744:10
>     frame #2: 0x0000000100222c62 Emacs`mark_frame(ptr=0x0000000105783630) at alloc.c:6321:20

This looks quite similar to gc crash that was fixed this summer, if I
recall correctly.  Are you still seeing these crashes in Emacs 28?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-10-30 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  2:02 bug#38936: 27.0.60; vector_marked_p: GC crash Mike Hamrick
2020-10-30 14:34 ` Lars Ingebrigtsen [this message]
2020-10-30 21:21   ` Mike Hamrick
2020-11-01 12:30     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lffng4v3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38936@debbugs.gnu.org \
    --cc=mikeh@muppetlabs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.