unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Issues using statprof  (no samples taken)
Date: Tue, 18 Nov 2008 23:02:45 +0100	[thread overview]
Message-ID: <87zljwheuy.fsf@gnu.org> (raw)
In-Reply-To: 4922EA36.7080905@mit.edu

Hello,

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 seems to be the only pthread_create call.  Looking through the
> gnucash source, the gnc-spawn-process-async call seems to be spinning
> up a separate process (well, thread in this case) to handle getting
> price quotes over the network...

Then it must be disappointed these days...  ;-)

Anyway, nothing to worry about.

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.

Thanks,
Ludo'.





  reply	other threads:[~2008-11-18 22:02 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 [this message]
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=87zljwheuy.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).