X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B5E3.2851A4E0@onstor-exch02.onstor.net>; Wed, 14 May 2008 09:54:21 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B5E3.2851A4E0"
Content-class: urn:content-classes:message
Subject: Will respin cougar build of submittal 22 
Date: Wed, 14 May 2008 09:54:21 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F0187@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Will respin cougar build of submittal 22 
Thread-Index: Aci14CU9+L40x8raSdO+TYzdDzQfrA==
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Cc: "Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Brian Stark" <brian.stark@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B5E3.2851A4E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

While running the acceptance tests I had a couple of crashes triggered =
by dmalloc. (defects were filed, BTW.)

The original plan was to release to QA submittal 22 with dmalloc =
enabled. After consulting with Tim and Jonathan the plan was revised a =
bit.

The plan now is to deliver submittal 22 with dmalloc built into the =
release but dmalloc will not be enabled by default in the runtime.=20

There is a simple way to turn off/on the dmalloc feature once you have a =
build with this capability. I will add the instruction on how to turn it =
on in the submittal notes.

I tested the build with and without dmalloc enabled.I need to make a =
change to one file that only requires me to run make release. (No =
rebuild of the nfx-tree is needed.)

I will be recreating the cougar distribution today.

Larry








------_=_NextPart_001_01C8B5E3.2851A4E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Will respin cougar build of submittal 22 </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>While running the acceptance tests I had a couple of =
crashes triggered by dmalloc. (defects were filed, BTW.)<BR>
<BR>
The original plan was to release to QA submittal 22 with dmalloc =
enabled. After consulting with Tim and Jonathan the plan was revised a =
bit.<BR>
<BR>
The plan now is to deliver submittal 22 with dmalloc built into the =
release but dmalloc will not be enabled by default in the runtime.<BR>
<BR>
There is a simple way to turn off/on the dmalloc feature once you have a =
build with this capability. I will add the instruction on how to turn it =
on in the submittal notes.<BR>
<BR>
I tested the build with and without dmalloc enabled.I need to make a =
change to one file that only requires me to run make release. (No =
rebuild of the nfx-tree is needed.)<BR>
<BR>
I will be recreating the cougar distribution today.<BR>
<BR>
Larry<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8B5E3.2851A4E0--
