AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071009173043.07a8f8b3@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<mike.lee@onstor.com>,<dl-Cougar@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E028FB5A7@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 9 Oct 2007 17:31:35 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Mike Lee" <mike.lee@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>
Subject: Re: common ssc core stack
Message-ID: <20071009173135.75372d56@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E028FB5A7@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E028FB5A7@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Stack corruption.  I thought all these were fixed?

One day someone is going to take my advice and use mpatrol.

# apt-get install mpatrolc (on your filer and it's not installed
already)

read the documentation

use it  (do we hand start these daemons or are they started from pm?
you might have to modify pmtab to start them with mpatrol)

easy-peasy


On Tue, 9 Oct 2007 17:24:07 -0700 "Mike Lee" <mike.lee@onstor.com>
wrote:

> 
> 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 
> defect 20651 - sanmd crash
> 
> So, I think we're seeing manifestations of the same problem.  
> 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
