[debbugs-tracker] bug#24884: closed (Segfault on (mkstemp! "XX" 0))

[GNU bug Tracking System]

Your message dated Wed, 01 Mar 2017 14:52:37 +0100
with message-id <address@hidden>
and subject line Re: bug#24884: Segfault on (mkstemp! "XX" 0)
has caused the debbugs.gnu.org bug report #24884,
regarding Segfault on (mkstemp! "XX" 0)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24884: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24884
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Segfault on (mkstemp! "XX" 0)
>
>
>
>
> Date: 
>
> Sat, 5 Nov 2016 21:16:58 +0300
>
>
>
>
> 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.
>
> Jean
>
> guile (GNU Guile) 2.0.13
> Copyright (C) 2016 Free Software Foundation, Inc.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#24884: Segfault on (mkstemp! "XX" 0)
>
>
>
>
> Date: 
>
> Wed, 01 Mar 2017 14:52:37 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
>
>
>
>
> On Wed 11 Jan 2017 22:33, Andy Wingo <address@hidden> writes:
>
> > On Sat 05 Nov 2016 19:16, Jean Louis <address@hidden> 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.)
>
> Sigh, spoke too soon.  This one turned out to be a rather more ordinary
> bug.  Fixed in git on both branches.  Thanks for the report!
>
> Andy
>
>
> --- End Message ---