X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B5E6.25619D98@onstor-exch02.onstor.net>; Wed, 14 May 2008 10:15:45 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Will respin cougar build of submittal 22 
Date: Wed, 14 May 2008 10:15:45 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09EE8298@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03B5B78E@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+TYzdDzQfrAABKzfrAAAoQzA=
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Vikas Saini" <vikas.saini@onstor.com>,
	"Larry Scheer" <larry.scheer@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>

The original reason for enabling dmalloc was to enable us to make
progress on a select set of defects that do not manifest themselves
easily.
The problem is that when dmalloc is enabled, the system is now crashing
immediately. We do not want to provide a submittal to QA that will block

all testing. Instead we want to create a submittal that has dmalloc
available but by default is turned off. This will allow dev to enable
dmalloc and debug the problems happening when the system is first
started.
Once we have fixed these problems we will ask QA to enable dmalloc on
the QA systems so we can get back to debugging the original defects.

> -----Original Message-----
> From: Vikas Saini
> Sent: Wednesday, May 14, 2008 10:06 AM
> To: Larry Scheer; Tim Gardner; Sandrine Boulanger
> Cc: Jonathan Goldick; Andy Sharp; Brian Stark; Paul Hammer
> Subject: RE: Will respin cougar build of submittal 22
>=20
> Larry,
> just curious...how does that help us. i am trying to understand the
> difference between enabling dmalloc by default versus enabling it
after
> upgrading to submittal. if we are seeing crashes triggered by dmalloc
then
> we will see them again as soon as we enable dmalloc.
>=20
> Thanks
> Vikas
>=20
>=20
>=20
> -----Original Message-----
> From: Larry Scheer
> Sent: Wed 5/14/2008 9:54 AM
> To: Tim Gardner; Vikas Saini; Sandrine Boulanger
> Cc: Jonathan Goldick; Andy Sharp; Brian Stark; Paul Hammer
> Subject: Will respin cougar build of submittal 22
>=20
> While running the acceptance tests I had a couple of crashes triggered
by
> dmalloc. (defects were filed, BTW.)
>=20
> 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.
>=20
> 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.
>=20
> 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.)
>=20
> I will be recreating the cougar distribution today.
>=20
> Larry
>=20
>=20
>=20
>=20
>=20
>=20
>=20

