From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: New articles on ewontfix
Date: Sun, 7 Jul 2013 17:52:26 +0200 [thread overview]
Message-ID: <CAPLrYESUPOdqGvpyJkYOYrmrzPfeeBgQt13tXkR5dF7bqZxH=g@mail.gmail.com> (raw)
In-Reply-To: <20130707152740.GY29800@brightrain.aerifal.cx>
2013/7/7 Rich Felker <dalias@aerifal.cx>:
> On Sun, Jul 07, 2013 at 02:20:15PM +0200, Szabolcs Nagy wrote:
>> * Rich Felker <dalias@aerifal.cx> [2013-07-05 11:54:11 -0400]:
>> > I'm still trying to determine how to work out a formal definition of
>> > library-safe. My thought is that it would be based on the property of
>> > being able to combine two programs with well-defined behavior, both
>> > using the library code, into a single program where each original
>> > program runs starting with its own initial thread, such that the
>> > combined program does not invoke UB and the two sub-programs match
>> > their behavior before being combined. However there are lots of ugly
>> > issues that have to be considered.
>> >
>> > With that done, the interesting part would be covering common failures
>> > of libraries to be library-safe.
>>
>> i'm not sure if you can derive all the interesting failures from a
>> single definition
>>
>> this definition covers multi-thread issues
Lukasz Sowa (blowfish diff for musl) has prepared a very good tool for
debugging multi-threaded applications.
https://github.com/luksow/Coconut
I hope that it will be useful in testing...
Daniel
next prev parent reply other threads:[~2013-07-07 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 16:48 Rich Felker
2013-07-04 17:50 ` Jeremy Huntwork
2013-07-04 17:58 ` Rich Felker
2013-07-05 15:31 ` Jeremy Huntwork
2013-07-05 15:45 ` Ivan Kanakarakis
2013-07-05 15:54 ` Rich Felker
2013-07-07 12:20 ` Szabolcs Nagy
2013-07-07 15:27 ` Rich Felker
2013-07-07 15:52 ` Daniel Cegiełka [this message]
2013-07-07 17:12 ` Szabolcs Nagy
2013-07-07 17:53 ` Rich Felker
2013-07-08 11:39 ` LM
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='CAPLrYESUPOdqGvpyJkYOYrmrzPfeeBgQt13tXkR5dF7bqZxH=g@mail.gmail.com' \
--to=daniel.cegielka@gmail.com \
--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).