unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.5.8 beta available for testing.
Date: Thu, 5 Sep 2002 14:08:43 +0200	[thread overview]
Message-ID: <15735.18763.141553.273633@meddo.cs.uu.nl> (raw)
In-Reply-To: <20020904.164324.74735108.Sven.Hartrumpf@FernUni-Hagen.de>

Sven.Hartrumpf@FernUni-Hagen.de writes:
> On 4 Sep 2002, Han-Wen Nienhuys <hanwen@cs.uu.nl> wrote: 
> > Sven writes:
> > > Impl.          Time   RAM
> > > SCM 5d6         5877s 386MB (The used SCM version is not optimized for speed.)
> > > Guile 1.5.8    13273s 971MB
> > > Guile 20020830 -      - (program runs for ever with a size of 258MB)
> > 
> > Is there some way for me to run this program over here in a debugger?
> No :-(
> > If that's not possible, then you could give us some hints. My hunch is
> > that GC is triggered in recent GUILEs too often, but I can't tell from
> > here if that is so, and why it does.
> How can I make the GC verbose?

Insert printfs in scm_igc () (gc.c) and scm_i_sweep_all_segments()
(gc-segment.c), the argument they take is the type of object being
allocated. Also, you could insert a

  scm_display(scm_gc_stats(), scm_current_error_port ())

at the end of scm_igc, halfway in scm_gc_for_newcell().

Also there's some printfs in gc-malloc.c that you could switch on.

--
Han-Wen Nienhuys   |   hanwen@cs.uu.nl    | http://www.cs.uu.nl/~hanwen/



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-09-05 12:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 13:34 Guile 1.5.8 beta available for testing Sven Hartrumpf
2002-08-28 14:21 ` Marius Vollmer
2002-08-28 14:38   ` Sven Hartrumpf
2002-08-28 15:34     ` Marius Vollmer
2002-08-28 16:21       ` Lynn Winebarger
2002-08-28 18:18     ` Han-Wen Nienhuys
2002-08-28 21:09       ` Sven Hartrumpf
2002-08-28 22:43         ` Han-Wen Nienhuys
2002-09-03  7:33         ` Sven Hartrumpf
2002-09-04 11:08           ` Han-Wen Nienhuys
2002-09-04 14:43             ` Sven Hartrumpf
2002-09-05 12:08               ` Han-Wen Nienhuys [this message]
2002-09-05 19:52                 ` Sven Hartrumpf
2002-09-03 11:14       ` Sven Hartrumpf
  -- strict thread matches above, loose matches on Subject: below --
2002-08-26 17:34 Rob Browning
2002-08-27  9:06 ` Lars J. Aas
2002-08-28 16:28   ` Marius Vollmer
2002-08-29  7:59     ` Lars J. Aas
2002-08-31 12:01       ` Marius Vollmer
2002-09-02 11:38         ` Lars J. Aas
2002-08-29 10:29 ` tomas
2002-08-29 16:22   ` Rob Browning
2002-08-29 17:18     ` tomas
2002-08-29 17:42     ` tomas
2002-08-29 17:49       ` Rob Browning
2002-08-29 18:04         ` Lynn Winebarger
2002-08-29 18:55         ` Marius Vollmer
2002-08-29 19:17           ` Lynn Winebarger
2002-08-29 19:24             ` Lynn Winebarger
2002-08-29 19:58             ` Marius Vollmer
2002-08-31 16:45       ` tomas
2002-08-29 18:49     ` Marius Vollmer

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/guile/

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

  git send-email \
    --in-reply-to=15735.18763.141553.273633@meddo.cs.uu.nl \
    --to=hanwen@cs.uu.nl \
    --cc=guile-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.
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).