From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c0567ec88842f790
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: Memory leak in porting VAX/VMS -> AXP/VMS
Date: 1996/04/11
Message-ID: <1996Apr11.192650.1@eisner>#1/1
X-Deja-AN: 147004288
x-nntp-posting-host: eisner.decus.org
references: <Mats.Weber-0904962310310001@mlma21.elca-matrix.ch>
x-nntp-posting-user: KILGALLEN
organization: LJK Software
newsgroups: comp.lang.ada
Date: 1996-04-11T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <Mats.Weber-0904962310310001@mlma21.elca-matrix.ch>, Mats.Weber@elca-matrix.ch (Mats Weber) writes:

> The program works fine on VAXes, but leaks lots of memory on the AXP. Has
> anyone else had the same problem ? Does anyone know of tools to locate
> such leaks on an AXP/VMS machine (DEC's heap analyser is for VAX/VMS only)
> ?

The Heap Analyzer used to be VAX-only, but with the latest release of
VMS it also works on Alpha.  See Section 4.3 on page 4-6 of the VMS V7.0
New Features Manual (AA-QSBFA-TE, December 1995).

Larry Kilgallen
LJK Software