From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Segmentation fault in scm_igc
Date: 07 Mar 2004 15:27:09 +0000 [thread overview]
Message-ID: <85ad2she42.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <877jy0g1lg.fsf@robotron.ath.cx>
David Hansen <david.hansen@physik.fu-berlin.de> writes:
> Hello,
>
> my first guile code started with a SIGSEGV. Not sure if
> it's not my fault but looks like a bug to me.
>
> ,----[ gtst.c ]
> | // -*- compile-command: "gcc -g -Wall `guile-config compile` `guile-config link` gtst.c -o gtst" -*-
> |
> | #include <libguile.h>
> |
> | int
> | main (void)
> | {
> | SCM str = scm_makfrom0str ("hello world");
> | return 0;
> | }
> `----
You need to follow a more particular model for your main function.
Please see node `A Sample Guile Main Program' in the manual.
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-03-07 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 13:53 Segmentation fault in scm_igc David Hansen
2004-03-07 15:27 ` Neil Jerram [this message]
2004-03-07 23:54 ` Marius Vollmer
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=85ad2she42.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@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).