From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: speaking of screenlock
Date: Thu, 15 Jul 2021 19:04:58 -0400 [thread overview]
Message-ID: <5DC2C69CF1837BEADA2CE21DC0DEBDF0@eigenstate.org> (raw)
In-Reply-To: <CABB-WO85Vy27QfK7pZ=Vt+REhDMiC9ERSRd0q3OaAryk18eNqg@mail.gmail.com>
Quoth Stuart Morrow <morrow.stuart@gmail.com>:
> Actually, I don't get what it is about screenlock in the first place
> that different procs can't access each other's malloc'd objects. It
> seems other programs can do this just fine.
>
See RFMEM in rfork(2). Though, I don't see
anything in screenlock that would prevent
it. What makes you think they can't access
each other's malloc'ed objects?
next prev parent reply other threads:[~2021-07-15 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 14:27 [9front] " Stuart Morrow
2021-07-15 21:47 ` [9front] " Stuart Morrow
2021-07-15 23:04 ` ori [this message]
2021-07-16 9:07 ` Stuart Morrow
2021-07-16 10:01 ` cinap_lenrek
2021-07-16 10:50 ` Stuart Morrow
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5DC2C69CF1837BEADA2CE21DC0DEBDF0@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).