Path: ...!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Joy of this, Joy of that Date: 28 Nov 2024 00:57:06 GMT Lines: 20 Message-ID: References: <6iKdnTQOKNh6AqD6nZ2dnZfqn_idnZ2d@earthlink.com> <20241120081039.00006d2a@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net cpvYYZ7UzbaasliVgjS2jQSMrBqjDWCi26jUOBMdtFijjbfgVn Cancel-Lock: sha1:MbWfysdrZZotvLfpeh/HETZepyE= sha256:bY+990il/DIaM4FMglhN7nytn67ZnBAxtSGMPmJfgzE= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Bytes: 2394 On Wed, 27 Nov 2024 23:59:36 +0000, Pancho wrote: > On 11/27/24 22:06, Lawrence D'Oliveiro wrote: >> On Wed, 27 Nov 2024 09:27:35 +0000, Pancho wrote: >> >>> I remember we ran a tool called Purify to spot this type of error, >>> amongst other errors. >>> Presumably that injected additional code to check reliably. >> >> As I understand it, Valgrind does it on your executable without source >> code changes. > > Yeah, It was 30 years ago, I think Purify modified binary code, not > source code, but I can't really remember. I just remember Purify was > brilliant.. I don't know if I would call it brilliant. We had a license for a while but didn't renew it since it was seldom used due to the complexity of setting up the instrumentation. I'd used BoundsChecker years ago and it was no prize either.