From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Fix for Mac OS X Garbage Collection Crashes
Date: 15 Oct 2003 11:08:49 -0400 [thread overview]
Message-ID: <jwvllrm5yqe.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <m21xtfmoua.fsf@owlbear.local>
>>> The problem is caused by a change to src/alloc.c about a month ago that
>>> causes garbage collection to crash under certain circumstances (when
>>> LISP_INT values are on the gcprolist) if GC_MARK_STACK is set to
>>> GC_USE_GCPROS_AS_BEFORE. The best way to fix the problem is probably to
>>> fix the bug introduced. I don't want to work on that. Instead I have now
>>
>> That's interesting. It needs definitely to be fixed. Could you
>> give us as much info about this problem as you've encountered during
>> your debugging effort ?
> I haven't spent much time on it. Sorry I cannot be any more specific
> than this: it crashed at line 5014 of src/alloc.c and at that time `obj'
> seemed to contain a LISP_INT value. I don't have a recipe for repeating
> the error. Sorry.
Is this `line 5014' the `if (CONS...)' line in mark_object in the
code below ?
case Lisp_Cons:
{
register struct Lisp_Cons *ptr = XCONS (obj);
if (CONS_MARKED_P (ptr)) break;
CHECK_ALLOCATED_AND_LIVE (live_cons_p);
and in the earlier email you mention it's linked to `when
LISP_INT values are on the gcprolist'. What gave you this impression ?
I understand you don't have time to work on this and I'm better
placed to do the work, but any additional hint can be helpful: this is
otherwise very difficult to track down.
Stefan
next prev parent reply other threads:[~2003-10-15 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 23:57 Fix for Mac OS X Garbage Collection Crashes Andrew Choi
2003-10-14 21:31 ` Stefan Monnier
2003-10-14 22:33 ` Andrew Choi
2003-10-15 15:08 ` Stefan Monnier [this message]
2003-10-15 15:45 ` Andrew Choi
2003-10-15 17:05 ` Stefan Monnier
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=jwvllrm5yqe.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).