From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] awk split(a[1], a)
Date: Wed, 12 Dec 2012 23:24:53 +0100 [thread overview]
Message-ID: <13ce764b901d6789ac912fb3e203b1da@rei2.9hal> (raw)
In-Reply-To: <daeeec78e3dda590bfbd94b149a22052@coraid.com>
it looks to me as if eriks contrib/awk and the changes from
9legacy *should* have the same bug that was reported. at least i
cannot find any obvious changes in the diffs that would fix it.
http://www.cs.princeton.edu/~bwk/btl.mirror/
also seems to have the bug.
a way to reproduce the problem was presented (just override
the data on free with some pattern and then run the awk snipped
from the original mail).
it would be good if someone else veryfy this.
--
cinap
next prev parent reply other threads:[~2012-12-12 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 7:13 cinap_lenrek
2012-12-10 8:20 ` cinap_lenrek
2012-12-10 13:13 ` erik quanstrom
2012-12-12 21:33 ` David du Colombier
2012-12-12 21:39 ` erik quanstrom
2012-12-12 22:24 ` cinap_lenrek [this message]
2012-12-12 22:31 ` erik quanstrom
2012-12-12 22:38 ` cinap_lenrek
2012-12-13 3:22 ` erik quanstrom
2012-12-13 3:35 ` cinap_lenrek
2012-12-13 3:37 ` erik quanstrom
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=13ce764b901d6789ac912fb3e203b1da@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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).