X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80AD3.DF2672A5@onstor-exch02.onstor.net>; Tue, 9 Oct 2007 16:24:07 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C80AD3.DF2672A5"
Content-class: urn:content-classes:message
Subject: common ssc core stack
Date: Tue, 9 Oct 2007 16:24:07 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E028FB5A7@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: common ssc core stack
Thread-Index: AcgK098jmD4/9WmiSQuOFK8Q3ghr0Q==
From: "Mike Lee" <mike.lee@onstor.com>
To: "dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

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


Hi Team:

In three of the ssc daemon crashes I've analyzed thus far, we're getting =
the same stack:

Program terminated with signal 6, Aborted.
#0  0x2b52ab04 in kill () from /lib/libc.so.6
(gdb) where
#0  0x2b52ab04 in kill () from /lib/libc.so.6
#1  0x2b52c200 in abort () from /lib/libc.so.6
#2  0x2b568454 in __fsetlocking () from /lib/libc.so.6
#3  0x2b568454 in __fsetlocking () from /lib/libc.so.6
Previous frame identical to this frame (corrupt stack?)
(gdb)
The instruction address on the stack frames are not the same, but the =
function names are.

Specifically, this stack was observed in:
defect 20632 - spm crash
defect 20649 - vsd crash=20
defect 20651 - sanmd crash

So, I think we're seeing manifestations of the same problem. =20
Please let me know if you have recommendations/insights on this symptom.
For now, I'm trying to reproduce the crash on a case-by-case basis.

Thanks.

-Mike

------_=_NextPart_001_01C80AD3.DF2672A5
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.7652.24">
<TITLE>common ssc core stack</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>Hi Team:<BR>
<BR>
In three of the ssc daemon crashes I've analyzed thus far, we're getting =
the same stack:<BR>
<BR>
Program terminated with signal 6, Aborted.<BR>
#0&nbsp; 0x2b52ab04 in kill () from /lib/libc.so.6<BR>
(gdb) where<BR>
#0&nbsp; 0x2b52ab04 in kill () from /lib/libc.so.6<BR>
#1&nbsp; 0x2b52c200 in abort () from /lib/libc.so.6<BR>
#2&nbsp; 0x2b568454 in __fsetlocking () from /lib/libc.so.6<BR>
#3&nbsp; 0x2b568454 in __fsetlocking () from /lib/libc.so.6<BR>
Previous frame identical to this frame (corrupt stack?)<BR>
(gdb)<BR>
The instruction address on the stack frames are not the same, but the =
function names are.<BR>
<BR>
Specifically, this stack was observed in:<BR>
defect 20632 - spm crash<BR>
defect 20649 - vsd crash<BR>
defect 20651 - sanmd crash<BR>
<BR>
So, I think we're seeing manifestations of the same problem.&nbsp;<BR>
Please let me know if you have recommendations/insights on this =
symptom.<BR>
For now, I'm trying to reproduce the crash on a case-by-case basis.<BR>
<BR>
Thanks.<BR>
<BR>
-Mike</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C80AD3.DF2672A5--
