From: Andy Wingo <wingo@pobox.com>
To: Jean Louis <bugs@gnu.support>
Cc: 24884@debbugs.gnu.org
Subject: bug#24884: Segfault on (mkstemp! "XX" 0)
Date: Wed, 11 Jan 2017 22:33:30 +0100 [thread overview]
Message-ID: <87a8ax8eol.fsf@pobox.com> (raw)
In-Reply-To: <20161105181658.GA2536@protected.rcdrun.com> (Jean Louis's message of "Sat, 5 Nov 2016 21:16:58 +0300")
On Sat 05 Nov 2016 19:16, Jean Louis <bugs@gnu.support> writes:
> I was just testing a function, and before I figured out what is
> happening, it is segfaulting on:
> (mkstemp! "XX" 0)
>
> I don't say, I am using it right. It should not segfault.
I agree. This is a pending topic in Guile. (The reason, of course:
mutating literal constants is not valid Scheme. Guile allocates
some constant literals in read-only memory. Mutating that memory, or
attempting to do so, segfaults, as you have seen. We should raise an
error instead.)
Andy
next prev parent reply other threads:[~2017-01-11 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 18:16 bug#24884: Segfault on (mkstemp! "XX" 0) Jean Louis
2016-11-11 14:06 ` Matt Wette
2017-01-11 21:33 ` Andy Wingo [this message]
2017-03-01 13:52 ` Andy Wingo
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=87a8ax8eol.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=24884@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).