From: Andy Wingo <wingo@pobox.com>
To: Anand Dixit <Anand.Dixit@Sun.COM>
Cc: guile-user@gnu.org
Subject: Re: seg fault with repeated function calls from C?
Date: Tue, 16 Dec 2008 23:23:57 +0100 [thread overview]
Message-ID: <m363lj21z6.fsf@pobox.com> (raw)
In-Reply-To: <1229447835.11638.3.camel@home-desktop> (Anand Dixit's message of "Tue, 16 Dec 2008 09:17:15 -0800")
On Tue 16 Dec 2008 18:17, Anand Dixit <Anand.Dixit@Sun.COM> writes:
>> I am calling a guile function from my C code. Its a fairly straight
>> forward implementation. However, as I keep calling this function a
>> number of times, it breaks at some point with a segmentation fault. Here
>> is the relevant portion :
Can we see a C-level backtrace? Things look OK to me on first glance.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-12-16 22:23 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 [this message]
2008-12-17 0:46 ` Anand Dixit
2008-12-17 2:46 ` Anand Dixit
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=m363lj21z6.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=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).