From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] awk: don't write an extra NUL past the end of a block
Date: Tue, 23 Jan 2024 18:45:31 +0100 [thread overview]
Message-ID: <F056E68DACC66F58F358BC3E2E6D2983@wopr.sciops.net> (raw)
In-Reply-To: <1BB2A50064EC90776DDB56DBF7AF1DF8@wopr.sciops.net>
On Tue Jan 23 17:53:35 +0100 2024, moody@posixcafe.org wrote:
> Maybe give onetrueawk a try and see if you can reproduce the
> crash there as well, and if not perhaps we should copy their fix.
Er, sorry; this doesn't happen with bioawk on plan9, which is
based on onetrueawk iirc before it got littered with c99 stuff.
Cheers,
qwx
next prev parent reply other threads:[~2024-01-23 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 7:44 Kristo
2024-01-23 16:53 ` Jacob Moody
2024-01-23 17:40 ` qwx
2024-01-23 17:45 ` qwx [this message]
2024-01-23 17:50 ` Jacob Moody
2024-01-23 18:47 ` Aw: " Alexander Shendi
2024-01-23 18:32 ` Kristo
2024-01-23 21:27 ` Jacob Moody
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=F056E68DACC66F58F358BC3E2E6D2983@wopr.sciops.net \
--to=qwx@sciops.net \
--cc=9front@9front.org \
/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).