unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org
Subject: Re: Running guile single-threaded?
Date: Sat, 30 May 2020 23:27:56 +0200	[thread overview]
Message-ID: <87lfl9ru3n.fsf@gnu.org> (raw)
In-Reply-To: d226c8a3-f66c-b47a-8802-c3972de6c417@gmail.com

Hi,

Matt Wette <matt.wette@gmail.com> skribis:

> On 5/17/20 8:27 AM, Caleb Ristvedt wrote:
>> I'm trying to use unshare() with the CLONE_NEWUSER flag, but this
>> requires that the process be single-threaded (otherwise I always get
>> EINVAL). /proc/<guile-pid>/task has 6 entries when I launch guile, 5
>> after disabling automatic finalization. I can't seem to find a way to
>> get that down to 1. Is this feasible?
>>
>> - reepca
>>
>
> I don't this is possible without building guile using --without-threads
> argument to configure.  Otherwise, the mutl-threaded gc is included.

Yeah, there’s the GC marker threads, the finalization thread, and the
signal thread (started on the first call to the ‘sigaction’ procedure).
It’s crowded there.

It wonder if Guile should offer a documented way to stop the
finalization thread (as with ‘scm_set_automatic_finalization_enabled’,
but from Scheme) and the signal thread.

Ludo’.




      parent reply	other threads:[~2020-05-30 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 15:27 Running guile single-threaded? Caleb Ristvedt
2020-05-17 15:39 ` Matt Wette
2020-05-17 16:58   ` Caleb Ristvedt
2020-05-30 21:27   ` Ludovic Courtès [this message]

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=87lfl9ru3n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@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).