From owner-oi-users Fri Mar 10 08:28:00 1995 Return-Path: oi-users-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17624 for oi-users-outgoing; Fri, 10 Mar 1995 08:28:00 -0800 Received: from marvin.boulder.openware.com (marvin.boulder.openware.com [192.245.99.138]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA17618 for ; Fri, 10 Mar 1995 08:27:57 -0800 Received: from garya.boulder.openware.com (garya.boulder.openware.com [198.135.223.34]) by marvin.boulder.openware.com (8.6.9/8.6.9) with ESMTP id JAA24918; Fri, 10 Mar 1995 09:25:26 -0700 Received: (from garya@localhost) by garya.boulder.openware.com (8.6.9/8.6.9) id JAA05225; Fri, 10 Mar 1995 09:13:29 -0700 Date: Fri, 10 Mar 1995 09:13:29 -0700 From: Gary Aitken Message-Id: <199503101613.JAA05225@garya.boulder.openware.com> To: avraad@nyqsdsn1.eq.gs.com, oi-users@freefall.cdrom.com Subject: Re: Purifying an OI app Sender: oi-users-owner@FreeBSD.org Precedence: bulk > Are there any tricks to using Purify with OI apps? > I have an app that works fine, but when I link it > with Purify (3.0a) and run it, it dumps core - it > never even displays the app window. Here is the > traceback: We found a bug in the error message extraction code which has been fixed in the 4.6 release. Don't know if this is tripping over it or not; it may be. Purify 2 didn't seem to catch it. Actually, to give credit where credit is due, Kam @ pure found it and reported it to us. I don't know if you can prevent it with a .purify file entry or not. I believe the error only occurred when attempting to look up invalid error messages, but we never had a repeatable test case; only some diffs from pure. Our original code was obviously wrong, and we applied the patch. There is an array of tables for different classes of error messages, and we were marching off the end of the array if we didn't find the message requested.