From owner-freebsd-stable@freebsd.org Thu Jun 4 11:47:42 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D6BA33656F for ; Thu, 4 Jun 2020 11:47:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d3tQ1s4Kz4Wqd for ; Thu, 4 Jun 2020 11:47:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 3B3252F435 for ; Thu, 4 Jun 2020 11:47:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f177.google.com with SMTP id q14so4871262qtr.9 for ; Thu, 04 Jun 2020 04:47:42 -0700 (PDT) X-Gm-Message-State: AOAM530Pj8iJjIh2mPdPXf+wS1oO1C0Luh8nip8CkKE3Ux1bjp5K5dAs TBKQ5ZJpQCUb43pl47gHQUVugBL58QIcUMDgFpE= X-Google-Smtp-Source: ABdhPJwk5TmkGUzKrjj3XtAEWjK6X/nl0Rb10LUfme1AM/LOCNuIJ/FXWk2TOr7qO368KLATUpFGWSZwXlRFaqpcKGY= X-Received: by 2002:ac8:36ec:: with SMTP id b41mr4073694qtc.53.1591271261668; Thu, 04 Jun 2020 04:47:41 -0700 (PDT) MIME-Version: 1.0 References: <9c5739d4-c10c-74a0-0f69-6b4cdc3e0dd7@studiokaraoke.co.id> In-Reply-To: From: Kyle Evans Date: Thu, 4 Jun 2020 06:47:30 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: LUA ERROR: memory allocation error: block too big To: Roderick , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 11:47:42 -0000 On Thu, Jun 4, 2020 at 5:53 AM Roderick wrote: > [...] > > OK, for putting LUA was invested many many hours, the FORTH was > done in 5 minutes and ist worst quality. > I'd easily debate this latter bit- the Forth is certainly higher quality. > But the booting and installation problems, that I had to solve in > a tricky way and with additional hardware, began with the LUA loader, > and are solved putting an old loader, as somenone in this thread noted. > Can you share a pointer to the problems you had? It would be highly unusual for swapping out the interpreter to cause problems of this nature. With the way loader is architected, most low-level details don't change with different interpreters, and it's incredibly likely you are looking at a problem that was caused way-independently of swapping out the interpreter. Plenty of things broke between FreeBSD 10/11 and 12 in loader-world as our loader universe got thoroughly rototilled and improved -- many of these things cannot be attributed to lua, but perhaps are because of the coincidental timing. Thanks, Kyle Evans