From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: make-struct critical section throw
Date: Tue, 13 Feb 2007 07:03:59 +1100 [thread overview]
Message-ID: <87lkj3ta6o.fsf@zip.com.au> (raw)
Another error thrown from within an SCM_CRITICAL_SECTION_START,
(define vv (make-vtable-vtable "" 0))
(define v (make-struct vv 0 (make-struct-layout "uw")))
(make-struct v 0 'x)
=> abort
scm_make_struct has a critical section around the struct
initialization, but when scm_struct_init tries to convert the symbol
'x (an initializer) with scm_to_ulong for the "u" type field, an error
can be thrown.
Anyone know why there's a critical section there? Was it to stop
signal handlers in the past seeing half-initialized data? Can it be
safely done outside a section now? I'm guessing yes. The gc won't
mind seeing garbage in SCMs fields in the data array, will it?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2007-02-12 20:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lkj3ta6o.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).