all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ningyu Shi <shiningyu@gmail.com>
Cc: 7318@debbugs.gnu.org
Subject: bug#7318: 23.2.50; Crash in GC system
Date: Fri, 16 Aug 2019 14:06:19 -0700	[thread overview]
Message-ID: <87o90oom5w.fsf@mouse.gnus.org> (raw)
In-Reply-To: <iuj1v735z8b.fsf@opteron0157.magma-da.com> (Ningyu Shi's message of "Tue, 02 Nov 2010 10:58:44 -0800")

Ningyu Shi <shiningyu@gmail.com> writes:

> There are several cases I can crash emacs, all ends up to the GC system. I provide two cases with backtraces.
>
> 1. Open emacs with about 10 files, and use global-auto-revert-mode. Then try to change the file content very quickly from outside of emacs. I do 'git checkout brancha' and 'git checkout branchb' very quickly. Watch for emacs to crash/freeze. In case of crash, the bt is
>
> #0  0x000000000059af40 in Fgarbage_collect () at alloc.c:5117
> #1  0x000000000060d909 in Fbyte_code (bytestr=8338641, vector=8338677, maxdepth=20) at bytecode.c:529
> #2  0x00000000005bbcf3 in funcall_lambda (fun=8338557, nargs=2, arg_vector=0x7fbff60f18) at eval.c:3220

(I'm going through old bug reports that have unfortunately gotten no
responses yet.)

This crash wasn't handled at the time, and as this was reported more
than six years ago, I don't think there's much chance of making any
progress here, so I'm closing this bug report.  If you're still seeing
similar crashes in modern Emacs versions, please reopen.

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





      reply	other threads:[~2019-08-16 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 18:58 bug#7318: 23.2.50; Crash in GC system Ningyu Shi
2019-08-16 21:06 ` Lars Ingebrigtsen [this message]

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=87o90oom5w.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=7318@debbugs.gnu.org \
    --cc=shiningyu@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 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.