From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Issues using statprof (no samples taken)
Date: Sat, 15 Nov 2008 00:31:02 +0100 [thread overview]
Message-ID: <87prkx28cp.fsf@gnu.org> (raw)
In-Reply-To: 491DBAE5.5060100@mit.edu
Hello,
Boris Zbarsky <bzbarsky@MIT.EDU> writes:
> I'm having a bit of a problem with using statprof. I checked it out
> from CVS (:pserver:anonymous@cvs.savannah.gnu.org:/sources/guile
> CVSROOT, guile/guile-statprof module). I left it in the checkout
> tree, and am using GUILE_LOAD_PATH to point to the files.
Beware, Guile's CVS repository is no longer used, so software in there
is essentially unmaintained.
As far as `statprof' is concerned, I would recommend using the one
available in Guile-Lib, since it's been maintained there for some time:
http://home.gna.org/guile-lib/ . I've used it successfully with 1.8 in
the past.
> I am using guile 1.6.8 on Mac OS X, installed via Macports.
Is there any particular reason why you don't use 1.8.x?
> Any ideas as to where I should look for what's going on here and why
> no samples are being taken? Could it have something to do with the
> way guile is loaded by the gnucash binary? Or with something the
> binary itself is doing?
Can you check whether SIGPROF is actually delivered and whether
`profile-signal-handler' gets called, e.g., by adding a `(display
"foo\n")' call there?
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-11-14 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 17:52 Issues using statprof (no samples taken) Boris Zbarsky
2008-11-14 23:31 ` Ludovic Courtès [this message]
2008-11-16 18:58 ` Boris Zbarsky
2008-11-17 15:10 ` Ludovic Courtès
2008-11-17 15:36 ` Boris Zbarsky
2008-11-17 16:02 ` Ludovic Courtès
2008-11-17 21:52 ` Boris Zbarsky
2008-11-18 10:30 ` Ludovic Courtès
2008-11-18 16:15 ` Boris Zbarsky
2008-11-18 22:02 ` Ludovic Courtès
2008-11-21 2:51 ` Boris Zbarsky
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=87prkx28cp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).