From: Mark H Weaver <mhw@netris.org>
To: David Pirotte <david@altosw.be>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: make-c-struct and pointer->string
Date: Sat, 30 Mar 2019 16:26:02 -0400 [thread overview]
Message-ID: <877ecg85xm.fsf@netris.org> (raw)
In-Reply-To: <20190326101419.340081fc@capac> (David Pirotte's message of "Tue, 26 Mar 2019 10:14:47 -0300")
Hi David,
David Pirotte <david@altosw.be> writes:
> Hello,
>
> guile 2.2.4.1-cdb19
>
> ,use (system foreign)
>
> ;; this fails
>
> scheme@(guile-user)> (make-c-struct (list '* '*) (list (string->pointer "hello ") (string->pointer "there!")))
> $16 = #<pointer 0x55a3d54d54d0>
> scheme@(guile-user)> (parse-c-struct $16 (list '* '*))
> $17 = (#<pointer 0x55a3d5d12170> #<pointer 0x55a3d5d0a640>)
> scheme@(guile-user)> (map pointer->string $17)
> $18 = ("?g?գU" "`!?գU")
The Guile manual states:
-- Scheme Procedure: string->pointer string [encoding]
Return a foreign pointer to a nul-terminated copy of STRING in the
given ENCODING, defaulting to the current locale encoding. The C
string is freed when the returned foreign pointer becomes
unreachable.
Note the last sentence. When the returned foreign pointer (object)
becomes unreachable, the C string is freed. The problem here is that
you're not keeping a reference to those foreign pointer objects.
If you look at the code in foreign.c, specifically
'scm_string_to_pointer' and 'scm_from_pointer', you'll see that the C
pointer is wrapped within a heap-allocated foreign pointer object, and a
finalizer is being set on that heap object. 'make-c-struct' copies the
C pointers from those foreign pointer objects, but not not keep a
reference to the objects themselves.
In a later message, you wrote:
> Following your explanation and example, I tried this and thought it would work then,
> but it also failed:
>
> GNU Guile 2.2.4.1-cdb19
> Copyright (C) 1995-2017 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> ,use (system foreign)
> scheme@(guile-user)> (define str-1 "Hello")
> scheme@(guile-user)> (define str-2 "there!")
> scheme@(guile-user)> (make-c-struct (list '* '*) (list (string->pointer str-1) (string->pointer str-2)))
> $2 = #<pointer 0x55ae02e57830>
> scheme@(guile-user)> (parse-c-struct $2 (list '* '*))
> $3 = (#<pointer 0x55ae02f9e3c0> #<pointer 0x55ae02f8b050>)
> scheme@(guile-user)> (map pointer->string $3)
> $4 = ("" "`\v?\x02?U")
Here are you specifically saving a reference to the Scheme string
objects, but that's not what's needed. What's needed is to hold
references to the foreign pointer objects returned by 'string->pointer'
for as long as the C strings are needed.
Regards,
Mark
next prev parent reply other threads:[~2019-03-30 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 13:14 make-c-struct and pointer->string David Pirotte
2019-03-28 15:15 ` Amirouche Boubekki
2019-03-28 15:42 ` Neil Jerram
2019-03-29 8:48 ` David Pirotte
2019-03-29 9:46 ` David Pirotte
2019-03-29 19:08 ` Neil Jerram
2019-03-28 15:48 ` David Pirotte
2019-03-30 20:26 ` Mark H Weaver [this message]
2019-03-31 10:38 ` David Pirotte
2019-04-01 6:23 ` Mark H Weaver
2019-04-01 8:50 ` Mark H Weaver
2019-04-02 18:03 ` David Pirotte
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=877ecg85xm.fsf@netris.org \
--to=mhw@netris.org \
--cc=david@altosw.be \
--cc=guile-devel@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).