mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Simple testing task - string functions
Date: Mon, 18 Apr 2011 14:20:31 +0200	[thread overview]
Message-ID: <4DAC2C8F.8060102@gmail.com> (raw)
In-Reply-To: <20110414231140.GO13185@brightrain.aerifal.cx>

On 04/15/2011 01:11 AM, Rich Felker wrote:
> On Thu, Apr 14, 2011 at 07:59:33PM +0200, Luka Marčetić wrote:
>> Hello again.
>> Attached is the solution to the task. The program seems to preform
>> as expected, but may still need double-checking.
>> The tests therein fail where expected when linked with various old
>> versions of musl. Note that although the program is designed to
>> allow tests to fail gracefully as suggested, this does not happen
>> due to bugs in function implementations in said old versions that
>> the program depends on. Rich and Chris have confirmed a bug in 0.7.6
>> that causes a segfault in the siglongjmp (longjmp to be exact). I'm
>> still waiting for confirmation of inability of version 0.7.5 to
>> dispose the same signal to a specified handler properly.
> Here's an idea for avoiding the sigsetjmp/siglongjmp bug: just use
> setjmp/longjmp, and use sigaction with SA_NODEFER to install the
> signal handler. Actually sigaction should always be used to install
> signal handlers, since signal is under-specified and you can't be sure
> how it will behave.
>
> Rich
Hey.
I've been away (I'll explain why in #musl). Anyway, thanks for the 
critique. I'll take your word and use sigaction further on. I may 
correct these tests too for GSoC if you think they'll prove useful.
Anyway, we'll talk. It's now up to you guys to accept/reject my proposal 
if I'm not mistaken.
Thanks
-Luka



  reply	other threads:[~2011-04-18 12:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10  4:45 Rich Felker
2011-04-10 12:08 ` Luka Marčetić
2011-04-10 15:25 ` JIghtuse
2011-04-10 15:34   ` Rich Felker
2011-04-10 15:46   ` keep discussion threads separate (was: Simple testing task - string functions) Solar Designer
2011-04-14 17:59 ` Simple testing task - string functions Luka Marčetić
2011-04-14 23:11   ` Rich Felker
2011-04-18 12:20     ` Luka Marčetić [this message]
2011-04-25 19:34     ` Unit tests Luka Marčetić
2011-04-26 19:14       ` Solar Designer
2011-04-27  0:32         ` Rich Felker
2011-04-27  0:42       ` Rich Felker
2011-04-27  6:29         ` Luka Marčetić
2011-04-29  5:36           ` Solar Designer
2011-04-29 11:54             ` Christian Neukirchen
2011-05-01 19:36               ` Solar Designer
2011-05-02  8:51                 ` Christian Neukirchen
2011-05-02 12:49                   ` Solar Designer
2011-05-02 13:02                     ` errno
2011-05-02 13:11                       ` Rich Felker
2011-05-02 13:30                         ` Solar Designer
2011-05-02 13:32                           ` Rich Felker
2011-05-02 13:52                             ` Solar Designer
2011-05-02 13:27                       ` Solar Designer

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=4DAC2C8F.8060102@gmail.com \
    --to=paxcoder@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).