unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Derek Upham <sand@blarg.net>
Cc: guile-devel@gnu.org
Subject: Re: Cygwin port of Guile 2.2
Date: Tue, 02 May 2017 21:35:59 +0200	[thread overview]
Message-ID: <8760hjt5k0.fsf@pobox.com> (raw)
In-Reply-To: <87ziew4836.fsf@priss.frightenedpiglet.com> (Derek Upham's message of "Mon, 01 May 2017 13:48:13 -0700")

On Mon 01 May 2017 22:48, Derek Upham <sand@blarg.net> writes:

> Running pthread_join() on a thread only guarantees that the thread has
> returned an exit value.

Would you mind providing a reference please?  It is not that I don't
believe you but I think it's important to know whether this is a bug in
Guile or in the pthreads implementation.

> the on_thread_exit() function has the comment
>
>   /* This handler is executed in non-guile mode. */
>
> at the top.  Can someone explain what that means and what the
> implications are?  How can I safely invoke the contained code from
> other contexts?

https://www.gnu.org/software/guile/manual/html_node/Initialization.html

Basically this code is not automatically traced by GC, it can't
allocate, and it can't call (most) libguile functions.

Andy



  reply	other threads:[~2017-05-02 19:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:45 Cygwin port of Guile 2.2 Mike Gran
2017-04-04 17:03 ` Eli Zaretskii
2017-04-14  8:35 ` Andy Wingo
2017-04-14 13:41   ` Derek Upham
2017-04-17  8:04     ` Andy Wingo
2017-04-17 15:05       ` Derek Upham
2017-05-01 20:48         ` Derek Upham
2017-05-02 19:35           ` Andy Wingo [this message]
2017-05-03  3:18             ` Derek Upham
2017-05-03  9:24               ` Andy Wingo
2017-05-03  9:39                 ` szgyg
2017-05-03 14:21                 ` Derek Upham
2017-05-09 19:08                   ` Andy Wingo
2017-05-12 14:13                     ` Derek Upham
2017-05-15 20:06                       ` Andy Wingo
2017-05-04  5:21               ` zv

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=8760hjt5k0.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=sand@blarg.net \
    /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).