unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Boris Zbarsky <bzbarsky@MIT.EDU>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Issues using statprof  (no samples taken)
Date: Thu, 20 Nov 2008 21:51:59 -0500	[thread overview]
Message-ID: <4926224F.8030402@mit.edu> (raw)
In-Reply-To: <87zljwheuy.fsf@gnu.org>

Ludovic Courtès wrote:
> Boris Zbarsky <bzbarsky@MIT.EDU> writes:
>> That doesn't seem to have any effect.  Interestingly, if I change the
>> setitimer call but NOT the sigaction call I see the program terminate
>> with an uncaught SIGPROF...  So clearly the sigaction is having _some_
>> effect.  Just not that of calling the handler.  ;)
> 
> Aaarg.

That's about how I feel.

> However, it would help if you used 1.8, as I'm not sure exactly how 1.6
> differs in that respect.  According to
> https://bugs.gentoo.org/show_bug.cgi?id=165492 , it is feasible to just
> switch to 1.8 and keep GnuCash happy.

I'll see if I can manage this, but 
http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail#guile_1.8.1 doesn't 
fill me with hope.  It'll certainly involve me hacking around in the 
Macports gnucash and recompiling it to look for "guile" as oppposed to 
"guile16" at the very least...  It also sounds like I'll need to compile 
guile 1.8 with some non-default options, at least according to those 
gentoo bug reports.  :(

-Boris




      reply	other threads:[~2008-11-21  2:51 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
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 [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

  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=4926224F.8030402@mit.edu \
    --to=bzbarsky@mit.edu \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).