GNU bug report logs - #17168
24.3.50; Segfault at mark_object

Previous Next

Package: emacs;

Reported by: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>

Date: Wed, 2 Apr 2014 07:45:05 UTC

Severity: important

Tags: moreinfo

Merged with 15583, 15688, 15719, 15972, 16278, 16521, 17167, 17184

Found in version 24.3.50

Done: Stefan Monnier <monnier <at> IRO.UMontreal.CA>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Daniel Colascione <dancol <at> dancol.org>
Cc: 17168 <at> debbugs.gnu.org
Subject: bug#17168: 24.3.50; Segfault at mark_object
Date: Mon, 07 Apr 2014 09:49:41 +0200

> The only viable equally simple approach is simply
> removing pure storage, and if pure storage works (it amounts to a
> primitive kind of generational GC), we might as well keep it.

I did not look into the order GC scans its roots so maybe this is a
silly request and you'd better disregard it.  Nevertheless here it is:

(1) Would it be possible to tell how many objects get marked exclusively
    by marking from pure storage?

(2) Would it be possible to tell how many objects get marked exclusively
    by marking from ambiguous roots, that is, due to using conservative
    collection?

Obviously, either (1) or (2) would be incorrect wrt the other, that is,
if an object gets marked from the stack and has been already marked from
pure storage that object would be counted under (1).  Still I think that
figures we'd get here could be useful.

martin
This bug report was last modified 11 years and 47 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.