From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from minnie.tuhs.org (minnie.tuhs.org [50.116.15.146]) by inbox.vuxu.org (Postfix) with ESMTP id 53275271BF for ; Mon, 20 May 2024 05:43:37 +0200 (CEST) Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id C712F43AC6; Mon, 20 May 2024 13:43:33 +1000 (AEST) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by minnie.tuhs.org (Postfix) with ESMTPS id 6DB8743AC2 for ; Mon, 20 May 2024 13:43:26 +1000 (AEST) Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a5a5c930cf6so659591266b.0 for ; Sun, 19 May 2024 20:43:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1716176605; x=1716781405; darn=tuhs.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/zA1v90ffnUWgVxOQD1e3VjT2SOF99Z3XcHy4+8nUvE=; b=FeN0ScSOsf2CRScdT4pIw9e3807RfbQCZhAvhHfPTAcdDAfghGoLOUDD1fcbrNJPDI QUwkhKGky+Yuh9NcjyoylVQrUnEyLFEFKLYfyprHosGKGLwo7SQQn+usdFz2ECLX77qv 7ue+fijDRjXHmeN/Ar5+6QS4RdJzntkLqVpGSGXlCt+iHwoSoLCRz7jxpjnUAguUhOg5 33qeskJ3UDBIQvbNc+UCxgp7iiLai7Nbv/5h0XNP9Zntu5ef6qk96Z4u5AQzG90TNWo9 Kov6T69n9pB6oYZd9i5egSKZMbiIgmA8Vd38G8AW4FyLbxnvSqHuWbxl66kC7Kbo8si6 jstg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716176605; x=1716781405; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/zA1v90ffnUWgVxOQD1e3VjT2SOF99Z3XcHy4+8nUvE=; b=qg+XCj1prrDX4JOFIeun80dr8Q42Z29m9+9rngdR+hmD10jRaKjVbZepW/SngtGkTL M7HxlzIuc6CrPWonS2+phRz+DmDLPdvLgoOjod4f4i0xC3WCx3Cudra3eP91NfqQAQ5G kUVC+nqvrpnvkulRCVOu1mGJdvegY6kKB44vkiiYR2LlXy/ZgLTgAQpPl3pC7bcSK2TW UHoSXUHnJ7RbEqgVoNd0j6zctMvFp0m05GVApnGjdh7+HHsMREWnoTKt+Pi0YIT8Nq+v m0mQjlnsF5TB4Z6mOXHho+VILpM5tJZ4D8ZUTvZnhhYt1PbLWc8BELoa8UIIWLz70rkw W+Ng== X-Forwarded-Encrypted: i=1; AJvYcCXGZsuWK4I207zSHl+kYZTPns6gKaTgXe/CvuaKFXTcN0JcSEE0EqPSblZMY4GicrieY0IxKUPImWyT7MHv X-Gm-Message-State: AOJu0Yxi2OUf6Hxxx84/Q6gp/KpCfcFy7Bw4Lt5yjNpcH1+oc27YtlbZ Q2eKLq9HE9p4hc2sk2bQpaW46Q9t4WArJVhR70reK6G+U6aSgx6w4EQ49ZlZxmxCNE0r8UaV4/2 mgi8uDpzIOsfOzV2C82pWpR+vqWvBsaAQeb6TBQ== X-Google-Smtp-Source: AGHT+IG8qGroPi9uEHtVaD9SSiwXgfSd5sRIt6Y0PKBdo/8XaXXuOkLJD9U7Ch0QzOfbct8FX8bJxi9MCxWJZledBIE= X-Received: by 2002:a17:907:c90:b0:a5c:dd34:25e7 with SMTP id a640c23a62f3a-a5cdd34266cmr683462566b.1.1716176604646; Sun, 19 May 2024 20:43:24 -0700 (PDT) MIME-Version: 1.0 References: <202405200319.44K3J2Jq117819@freefriends.org> In-Reply-To: <202405200319.44K3J2Jq117819@freefriends.org> From: Warner Losh Date: Sun, 19 May 2024 21:43:11 -0600 Message-ID: To: Arnold Robbins Content-Type: multipart/alternative; boundary="000000000000e466170618da8040" Message-ID-Hash: W6JPEGLOKNCHHZQEFLVKD2JOLTLZ6BGG X-Message-ID-Hash: W6JPEGLOKNCHHZQEFLVKD2JOLTLZ6BGG X-MailFrom: wlosh@bsdimp.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Douglas McIlroy , The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: The 'usage: ...' message. (Was: On Bloat...) List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000e466170618da8040 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 19, 2024, 9:19=E2=80=AFPM wrote: > Rob Pike wrote: > > > The Cornell PL/I compiler, PL/C, ran on the IBM 360 so of course used > batch > > input. It tried automatically to keep things running after a parsing > error > > by inserting some token - semicolon, parenthesis, whatever seemed best = - > > and continuing to parse, in order to maximize the amount of input that > > could be parsed before giving up. At least, that's what I took the > > motivation to be. It rarely succeeded in fixing the actual problem, > despite > > PL/I being plastered with semicolons, but it did tend to ferret out mor= e > > errors per run. I found the tactic helpful. > > > > -rob > > Gawk used to do this, until people started fuzzing it, causing cascading > errors and eventually core dumps. Now the first syntax error is fatal. > It got to the point where I added this text to the manual: > > In recent years, people have been running "fuzzers" to generate > invalid awk programs in order to find and report (so-called) > bugs in gawk. > > In general, such reports are not of much practical use. The > programs they create are not realistic and the bugs found are > generally from some kind of memory corruption that is fatal > anyway. > > So, if you want to run a fuzzer against gawk and report the > results, you may do so, but be aware that such reports don=E2=80= =99t > carry the same weight as reports of real bugs do. > > (Yeah, I've just changed the subject, feel free to stay on topic. :-) > Awk bailing out near line 1. Warner > Arnold > --000000000000e466170618da8040 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 19, 2024, 9:19=E2=80=AFPM <arnold@skeeve.com> wrote:
Rob Pike <robpike@gmail.com> wrote:

> The Cornell PL/I compiler, PL/C, ran on the IBM 360 so of course used = batch
> input. It tried automatically to keep things running after a parsing e= rror
> by inserting some token - semicolon, parenthesis, whatever seemed best= -
> and continuing to parse, in order to maximize the amount of input that=
> could be parsed before giving up. At least, that's what I took the=
> motivation to be. It rarely succeeded in fixing the actual problem, de= spite
> PL/I being plastered with semicolons, but it did tend to ferret out mo= re
> errors per run. I found the tactic helpful.
>
> -rob

Gawk used to do this, until people started fuzzing it, causing cascading errors and eventually core dumps. Now the first syntax error is fatal.
It got to the point where I added this text to the manual:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 In recent years, people have been running "= ;fuzzers" to generate
=C2=A0 =C2=A0 =C2=A0 =C2=A0 invalid awk programs in order to find and repor= t (so-called)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 bugs in gawk.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 In general, such reports are not of much practi= cal use. The
=C2=A0 =C2=A0 =C2=A0 =C2=A0 programs they create are not realistic and the = bugs found are
=C2=A0 =C2=A0 =C2=A0 =C2=A0 generally from some kind of memory corruption t= hat is fatal
=C2=A0 =C2=A0 =C2=A0 =C2=A0 anyway.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 So, if you want to run a fuzzer against gawk an= d report the
=C2=A0 =C2=A0 =C2=A0 =C2=A0 results, you may do so, but be aware that such = reports don=E2=80=99t
=C2=A0 =C2=A0 =C2=A0 =C2=A0 carry the same weight as reports of real bugs d= o.

(Yeah, I've just changed the subject, feel free to stay on topic. :-)

Awk bailing out near line 1.

Warner=C2=A0
Arnold
--000000000000e466170618da8040--