Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc,alt.folklore.computers Subject: Re: naughty Python Date: 5 Jan 2026 19:20:36 GMT Lines: 39 Message-ID: References: <79ScnZHy-uXnP8n0nZ2dnZfqnPadnZ2d@giganews.com> <4oycne7Wk4RQ6sj0nZ2dnZfqnPidnZ2d@giganews.com> <10j48fv$2t1h9$12@dont-email.me> <10j5qgf$3etcd$6@dont-email.me> <10j60bb$3hhps$1@dont-email.me> <10j6n9s$3q8au$2@dont-email.me> <10j71fr$3rnk5$1@paganini.bofh.team> <10j88fb$at2l$2@dont-email.me> <20260102084925.000040b5@gmail.com> <10j9dis$mp8i$15@dont-email.me> <10j9f57$ovkv$2@dont-email.me> <10ja075$ukrb$2@dont-email.me> <10jdv8g$22nf7$3@dont-email.me> <7pI6R.1243339$79B9.954735@fx14.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net Auky6R+O44XQ0/vGqxv39gV9yVZ1Y0qFm5PJUDVvNYTlJgtYOk Cancel-Lock: sha1:brf84Z5ZNC2GXjTvNkPf8zLdXNw= sha256:i7/zVWL6aqu/lyk31sCxT0paHgrruNZv6Wn9Rf1PMF8= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:80531 alt.folklore.computers:233208 On Mon, 05 Jan 2026 05:57:23 GMT, Charlie Gibbs wrote: > On 2026-01-05, rbowman wrote: > >> On Sun, 04 Jan 2026 19:41:12 GMT, Charlie Gibbs wrote: >> >>> On 2026-01-04, Niklas Karlsson wrote: >>> >>>> On 2026-01-04, Peter Flass wrote: >>>> >>>>> I look at some code and wonder "how the heck has this ever worked?", >>>>> but the answer is that no one ever hit that combination of things >>>>> before, or used that option. >>>> >>>> That's certainly the sensible explanation, but I've had scenarios >>>> like that, even with my own code from the past, where I could swear >>>> up and down that I myself had successfully used that code in the >>>> exact scenario that would obviously break. >>> >>> Yup. Sounds like a Schrodinbug. It should have never worked, but it >>> does until you look at it - and then it never works again. >> >> Conversely, it fails until you log a debug statement to see what's >> going on and it works. I'd never, never just leave the debug in place, >> no siree. > > Unless the customer is screaming for a fix RIGHT NOW. > > But I'd go back and try to track it down once he's pacified. It's been a day or three but I think I did. iirc it also had the charming feature of only manifesting in the Windows build, not in Linux where I had valgrind and electric fence. Another mystery is why memory debuggers on Windows are expensive and barely usable. We had a Purify license but configuring the instrumentation was such a hassle it was rarely used. When the license came up for renewal nobody spoke up to keep it. BoundsChecker reportedly is even worse.