From owner-freebsd-tcltk@freebsd.org Thu Mar 14 19:10:18 2019 Return-Path: Delivered-To: freebsd-tcltk@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDD6B152807B for ; Thu, 14 Mar 2019 19:10:17 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin2.langille.org (clavin2.langille.org [199.233.228.197]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "clavin.langille.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4EFF8D2AB; Thu, 14 Mar 2019 19:10:16 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin2.int.langille.org (clavin2.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id 4DF1C492B4 ; Thu, 14 Mar 2019 19:10:15 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: 2019Q1 - can't set "doc": var is read-only From: Dan Langille In-Reply-To: <20190314093551.bsnskmsgnulvh6dw@ptrcrt.ch> Date: Thu, 14 Mar 2019 15:10:14 -0400 Cc: freebsd-tcltk@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6F6FB074-C527-4304-864B-9C3BF8E45AB7@langille.org> References: <49F7A94D-FC3D-458A-B787-DF424D496E81@langille.org> <20190314093551.bsnskmsgnulvh6dw@ptrcrt.ch> To: Pietro Cerutti X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: B4EFF8D2AB X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=langille.org; spf=pass (mx1.freebsd.org: domain of dan@langille.org designates 199.233.228.197 as permitted sender) smtp.mailfrom=dan@langille.org X-Spamd-Result: default: False [-6.38 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:199.233.228.197]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-3.16)[ip: (-9.69), ipnet: 199.233.228.0/22(-2.13), asn: 36236(-3.90), country: US(-0.07)]; MX_GOOD(-0.01)[cached: ALT3.ASPMX.L.GOOGLE.COM]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[langille.org,none]; NEURAL_HAM_SHORT(-0.92)[-0.917,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:199.233.228.0/22, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-tcltk@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Tcl/Tk discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2019 19:10:18 -0000 > On Mar 14, 2019, at 5:35 AM, Pietro Cerutti wrote: >=20 > On Mar 13 2019, 18:15 UTC, Dan Langille wrote: >> One of our in-house tcl applications is getting an error: >>=20 >> % set sec_comp [$test createComponent security #auto 1 2] >> can't set "doc": var is read-only >=20 > Hi Dan, >=20 > which version of Tcl are you using? 8.6.9 > I assume your in-house application uses the C interface to Tcl, not = just Tcl as a scripting language. If that's the case, the error you're = seeing is similar to what you'd get if you tryied to write to a linked = variable defined as read-only: >=20 > http://tcl.tk/man/tcl8.7/TclLib/LinkVar.htm >=20 > Does this sound familiar? I think this is all Tcl. I'm not the dev, I'm just trying to help them = figure out why the code stopped working on 2019Q1. >=20 > Alternatively, you might have a trace set up to intercept writes to a = variable, but that'd need to be either in your code or in some Tcl code = you're using as a pkg. Example: > http://core.tcl.tk/tcl/artifact/a057a170260b246e?ln=3D733,740 >=20 >> In a test environment, I have narrowed it down to something between = 2018Q4 and 2019Q1 >>=20 >> The devs say "something changed" and an internal structure they used = to write to can no longer be written to. >>=20 >> Does this ring any bells to folks? >=20 > Internal to Tcl? Doesn't make any rings bell here :( >=20 >> I'm going to start updating pkgs one by one to see which one breaks = it, but wanted feedkback in case this is a known issue. >>=20 >> My searches fail. >>=20 >> Thank you. >=20 > Let me know if I can help any further. I've been on #tcl on FreeNode, conversing with the tDOM maintainer. = They have been able to create a test case which reproduces the issue on = 0.9.1, but not on 0.9.0 The change was done to produce an error if the code was doing the wrong = thing. My issue: we're using third party code which is unlikely to get = updated any time soon. I've been pointed to a non-release branch, so we see if that helps. --=20 Dan Langille - BSDCan / PGCon dan@langille.org