mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Guided Muscle <atguarded-gizmo@yahoo.com>
To: <musl@lists.openwall.com>
Subject: Re: Musl bug, or, am I losing my mind?
Date: Thu, 31 Dec 2015 19:59:33 +0000 (UTC)	[thread overview]
Message-ID: <786818513.4541881.1451591973977.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <786818513.4541881.1451591973977.JavaMail.yahoo.ref@mail.yahoo.com>

Hi Rich,
Awesome.
BTW, I'm only reporting what I have done. I hope it helped.
Thanks
--
GM

--------------------------------------------
On Thu, 12/31/15, Rich Felker <dalias@libc.org> wrote:

 Subject: Re: [musl] Musl bug, or, am I losing my mind?
 To: musl@lists.openwall.com
 Date: Thursday, December 31, 2015, 2:45 PM
 
 On Thu, Dec 31, 2015 at 07:35:38PM
 +0000, Guided Muscle wrote:
 > Oh, I wanted to add that this is probably not a cdb bug
 because cdb,
 > when compiled with gcc or clang, worked for i >
 25000.
 
 That doesn't necessarily tell you anything. If the program
 is
 producing undefined behavior, it could appear to work under
 arbitrary
 conditions. Or it might not be producing undefined behavior
 but rather
 just making invalid assumptions about the implementation.
 
 I just tried your test.lua with tinycdb I built myself on
 Alpine Linux
 (x86_64) and could not reproduce the problem. cdb succeeded
 just fine
 reading from pipe. I tried both piping directly from lua,
 and saving
 the output to a file then piping from cat and neither
 produced an
 error.
 
 Rich
 


       reply	other threads:[~2015-12-31 19:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <786818513.4541881.1451591973977.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 19:59 ` Guided Muscle [this message]
     [not found] <2021478498.4444333.1451595055186.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 20:50 ` Guided Muscle
     [not found] <1229082331.4470232.1451594892445.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 20:48 ` Guided Muscle
     [not found] <2036560950.4461281.1451590538227.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 19:35 ` Guided Muscle
2015-12-31 19:45   ` Rich Felker
     [not found] <1163254146.4344492.1451589596849.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 19:19 ` Guided Muscle
     [not found] <1315337459.141890.1451583062461.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 17:31 ` Guided Muscle
2015-12-31 18:33   ` Rich Felker
2015-12-31 20:34   ` Szabolcs Nagy
2015-12-31 20:35     ` Rich Felker
     [not found] <1535596338.4389758.1451579882141.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31 16:38 ` Guided Muscle
     [not found] <1295998941.4272196.1451543795605.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-31  6:36 ` Guided Muscle
2015-12-31 11:42   ` Szabolcs Nagy
2015-12-31 11:53     ` Szabolcs Nagy
     [not found] <1337210970.4152546.1451505881575.JavaMail.yahoo.ref@mail.yahoo.com>
2015-12-30 20:04 ` Guided Muscle
2015-12-30 21:28   ` Szabolcs Nagy
2015-12-31  3:10     ` Szabolcs Nagy
2015-12-31  4:07       ` Rich Felker
2015-12-31 12:10   ` Szabolcs Nagy

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=786818513.4541881.1451591973977.JavaMail.yahoo@mail.yahoo.com \
    --to=atguarded-gizmo@yahoo.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).