From: Anand Dixit <Anand.Dixit@Sun.COM>
To: guile-user@gnu.org
Subject: Re: seg fault with repeated function calls from C?
Date: Tue, 16 Dec 2008 18:46:35 -0800 [thread overview]
Message-ID: <1229481995.11638.53.camel@home-desktop> (raw)
In-Reply-To: <1229474764.11638.28.camel@home-desktop>
Hi all,
I was using a few deprecated commands from the 'gh_' interface
(specifically gh_enter and gh_scm2newstr). On a hunch, I converted those
to scm calls, removed the include for guile/gh.h and now I don't have
any trouble even with 5million calls to scm_call_4. The question now is
if the problem was related to the gh_ functions interacting in some way
or have I just postponed when I see the problem again. After all, the
segment that was giving segmentation fault was not making any explicit
gh_ calls.
Thanks,
- Anand
prev parent reply other threads:[~2008-12-17 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 6:22 seg fault with repeated function calls from C? Anand Dixit
2008-12-16 17:17 ` Anand Dixit
2008-12-16 20:08 ` Ludovic Courtès
2008-12-17 0:23 ` Anand Dixit
2008-12-17 10:28 ` Neil Jerram
2008-12-16 22:23 ` Andy Wingo
2008-12-17 0:46 ` Anand Dixit
2008-12-17 2:46 ` Anand Dixit [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=1229481995.11638.53.camel@home-desktop \
--to=anand.dixit@sun.com \
--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).