From: William Pitcock <nenolod@dereferenced.org>
To: musl@lists.openwall.com
Subject: Re: getcontext, setcontext, makecontext and swapcontext
Date: Mon, 29 Jan 2018 09:38:00 -0600 [thread overview]
Message-ID: <CA+T2pCHL=zqFG_08SYkOJe2Lw1dyBtzmZDmbffkbNsWCeNxG_g@mail.gmail.com> (raw)
In-Reply-To: <trinity-faee7cc1-b4b2-493a-8b01-744bed68767c-1517142298690@3c-app-mailcom-lxa01>
Hi,
On Sun, Jan 28, 2018 at 6:24 AM, Tmp File <tmpfile@mail.com> wrote:
> Hello all.
>
> I'm compiling many software in a musl box and (by far) the biggest wall I hit regards the functions getcontext, setcontext, makecontext and swapcontext. I understand they are deprecated, but they are used in many programs and it's usually really troublesome/tricky to modify the upstream source code to accomodate for them being unavailable on musl.
>
> David du Colombier from plan9port mentioned[0] a simple coroutine library called libstak[1] that should help.
> I see 2 possible approaches:
> (i) musl imports libstak
> (ii} users somehow compile libstak and make it available for programs that need the *context functions
>
> In case you aren't interested in (i) could somebody help us get (ii) to work?
> Then musl distros like Alpine could have libstak as some kind of "compatibility" layer.
> Of course (i) might be a better solution, if you aren't so concerned about getcontext, setcontext, makecontext and swapcontext "deprecation status".
Unfortunately, libtask does not actually contain/provide getcontext()
or setcontext(). It only provides makecontext() and swapcontext().
Implementing a library that has these functions is on my todo list.
William
next prev parent reply other threads:[~2018-01-29 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 12:24 Tmp File
2018-01-29 15:38 ` William Pitcock [this message]
2018-01-29 18:47 ` Rich Felker
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='CA+T2pCHL=zqFG_08SYkOJe2Lw1dyBtzmZDmbffkbNsWCeNxG_g@mail.gmail.com' \
--to=nenolod@dereferenced.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).