From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org, bug-guile@gnu.org
Subject: Re: Segfault on setting file-position on sockets
Date: Mon, 20 May 2002 13:54:56 -0700 [thread overview]
Message-ID: <E179uBD-0008RH-00@giblet> (raw)
In-Reply-To: <20020520144321.GA29136@duronbox.nosuchnet> (message from Arno Peters on Mon, 20 May 2002 16:43:21 +0200)
From: Arno Peters <a.w.peters@ieee.org>
Date: Mon, 20 May 2002 16:43:21 +0200
The following 2 line snippet will segfault guile 1.4
(let ((sock (socket AF_INET SOCK_STREAM 0)))
(file-set-position sock 0))
thanks. this is now recorded in the bugs db as:
1005-fseek-0-on-socket-dumps-core
cvs HEAD and branch_release-1-6 signal "ERROR: unbound variable: fseek"
but do not segfault.
[bug-guile added to cc.]
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
parent reply other threads:[~2002-05-20 20:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20020520144321.GA29136@duronbox.nosuchnet>]
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=E179uBD-0008RH-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).