From: Linas Vepstas <linasvepstas@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25498@debbugs.gnu.org
Subject: bug#25498: Crash in open-file; patch attached
Date: Wed, 15 Feb 2017 02:28:24 -0600 [thread overview]
Message-ID: <CAHrUA34TkrMYRj=QUZhDirayvKCvkafgsG_ddd=A141FNQJLeg@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA374WKsWozV2si+Gh4H9eN229VxXHwdcy2WKJBWz8c3b4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
Specifically, this crashes, now: GNU Guile 2.1.6.10-710eb
On Wed, Feb 15, 2017 at 2:25 AM, Linas Vepstas <linasvepstas@gmail.com>
wrote:
> I'm using version 2.1 pulled from git, maybe a few days or week before the
> bug was opened.
>
> On Sat, Feb 11, 2017 at 3:10 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hi Linas,
>>
>> Linas Vepstas <linasvepstas@gmail.com> skribis:
>>
>> > The following crashes instantly; I used single-quotes by accident.
>> >
>> > (open-file "/tmp/lg" 'w')
>> >
>> > Stack:
>> >
>> > Enter `,help' for help.
>> > scheme@(guile-user)> (open-file "/tmp/lg" 'w')
>> >
>> > Thread 1 "guile" received signal SIGSEGV, Segmentation fault.
>> > scm_i_mode_to_open_flags (mode=mode@entry=0x555555ac5660,
>> > is_binary=is_binary@entry=0x7fffffffd46c,
>> > FUNC_NAME=FUNC_NAME@entry=0x7ffff7b89a7d "open-file")
>> > at ../../libguile/fports.c:168
>>
>> What version of Guile are you using? With 2.0.13, I get:
>>
>> --8<---------------cut here---------------start------------->8---
>> scheme@(guile-user)> (open-file "/tmp/lg" 'w')
>> ERROR: In procedure open-file:
>> ERROR: In procedure open-file: Value out of range: w'
>> --8<---------------cut here---------------end--------------->8---
>>
>> Ludo’.
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2192 bytes --]
next prev parent reply other threads:[~2017-02-15 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 0:34 bug#25498: Crash in open-file; patch attached Linas Vepstas
2017-02-11 21:10 ` Ludovic Courtès
2017-02-15 8:25 ` Linas Vepstas
2017-02-15 8:28 ` Linas Vepstas [this message]
2017-03-01 16:37 ` 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='CAHrUA34TkrMYRj=QUZhDirayvKCvkafgsG_ddd=A141FNQJLeg@mail.gmail.com' \
--to=linasvepstas@gmail.com \
--cc=25498@debbugs.gnu.org \
--cc=ludo@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).