X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B6D9.65D34C48@onstor-exch02.onstor.net>; Thu, 15 May 2008 15:17:01 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B6D9.65D34C48"
Content-class: urn:content-classes:message
Subject: RE: ssc cores
Date: Thu, 15 May 2008 15:17:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09FCF139@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ssc cores
Thread-Index: Aci1F/EwaU0EC7otSre3NYgpvGYxGQAAOGQwAABIEIAAAB8wYAAALUqgAAAPMFAAb2ktoA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E09EE7CFA@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09EE7D09@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09EE7D20@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09EE7D31@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09EE7D3E@onstor-exch02.onstor.net> 
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "dl-Software" <dl-software@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B6D9.65D34C48
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Update:

You need to mount the unstripped binaries and libraries on BSD as well.
Raj just had a case when he could not get correct stack trace on BSD
without mounting.

_____________________________________________
From: Maxim Kozlovsky=20
Sent: Tuesday, May 13, 2008 10:06 AM
To: John Keiffer; dl-Software; dl-QA
Subject: RE: ssc cores

Yes, mount the build-tree paths on the filer and run the gdb as usual.
The build tree directories have the libraries and binaries with all
debug information.

_____________________________________________
From: John Keiffer=20
Sent: Tuesday, May 13, 2008 10:04 AM
To: Maxim Kozlovsky; dl-Software; dl-QA
Subject: RE: ssc cores

Okay. Are you saying that we should mount those paths directly on the
filer, and then run GDB like we used to? Or are you saying we should
mount those on a client and run some other command?

_____________________________________________
From: Maxim Kozlovsky=20
Sent: Tuesday, May 13, 2008 10:01 AM
To: John Keiffer; dl-Software; dl-QA
Subject: RE: ssc cores

The page describes what used to work on BSD. The compiler and gdb on
linux is more recent revision (which does not always mean better), and
based on what is happening it looks like it can't get the stack trace
right without all the debug information. So yes the page needs to be
updated with what I've just described.

_____________________________________________
From: John Keiffer=20
Sent: Tuesday, May 13, 2008 9:57 AM
To: Maxim Kozlovsky; dl-Software; dl-QA
Subject: RE: ssc cores

If we do a gdb directly on the filer for daemon core files, then why
does it not work as it should? I believe that this is what everyone does
in QA. Based on what you are saying it sounds like this process is not
valid.

Does this page need to be modified?
http://wiki.onstor.net/wiki/Coredump_and_crashdump#Daemon_core_file

Thanks,
John

_____________________________________________
From: Maxim Kozlovsky=20
Sent: Tuesday, May 13, 2008 9:47 AM
To: Maxim Kozlovsky; dl-Software; dl-QA
Subject: RE: ssc cores

Here is an example how to mount directories to get correct stacktrace:

10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050608-sub21/nfx-
tree on /mnt type nfs (rw,addr=3D10.0.0.236)
10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050608-sub21/nfx-
tree/Build/cg/opt/bin on /onstor/bin type nfs (rw,addr=3D10.0.0.236)
10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050608-sub21/nfx-
tree/Build/cg/opt/lib on /onstor/lib type nfs (rw,addr=3D10.0.0.236)
_____________________________________________
From: Maxim Kozlovsky=20
Sent: Tuesday, May 13, 2008 9:40 AM
To: dl-Software; dl-QA
Subject: ssc cores

Hello,

When you are trying to get the SSC core backtrace for a defect please
remember to mount the libraries and binaries with the debugging
information, otherwise the stack trace may be not quite right. See
example below.

Max

Here is what was reported in 21892:

#0  0x2b5b5104 in kill () at ../string/bits/string2.h:998
#1  0x2b5b670c in *__GI_abort () at ../sysdeps/generic/abort.c:88
#2  0x2b5f111c in __libc_message (do_abort=3D2, fmt=3D0x2b6c0878 "*** =
glibc
detected *** %s: 0x%s ***\n")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:145
#3  0x2b5f7e7c in malloc_printerr (action=3D3, str=3D0x2b6c0a4c =
"malloc():
memory corruption", ptr=3D<value optimized out>) at malloc.c:5525
#4  0x2b5fa4a0 in _int_malloc (av=3D0x2b70eba0, bytes=3D<value optimized
out>) at malloc.c:3933
#5  0x2b5fdd5c in __libc_calloc (n=3D<value optimized out>,
elem_size=3D<value optimized out>) at malloc.c:3647
#6  0x0042e9d0 in evm_allocLunEntry ()
#7  0x0044b1d8 in evm_getVolLunList ()
#8  0x0044d378 in evm_procSpmRsp ()
#9  0x00409f28 in evm_processMsg ()
#10 0x00405884 in evm_closeSess ()
#11 0xffffffffffffff00 in ?? ()

Correct stack trace looks like this:

#0  0x2b5b5104 in kill () at ../string/bits/string2.h:998
#1  0x2b5b670c in *__GI_abort () at ../sysdeps/generic/abort.c:88
#2  0x2b5f111c in __libc_message (do_abort=3D2, fmt=3D0x2b6c0878 "")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:145
#3  0x2b5f7e7c in malloc_printerr (action=3D3, str=3D0x2b6c0a4c "\n",=20
    ptr=3D<value optimized out>) at malloc.c:5525
#4  0x2b5fa4a0 in _int_malloc (av=3D0x2b70eba0, bytes=3D<value optimized
out>)
    at malloc.c:3933
#5  0x2b5fdd5c in __libc_calloc (n=3D<value optimized out>,=20
    elem_size=3D<value optimized out>) at malloc.c:3647
#6  0x0042e9d0 in evm_allocLunEntry (sid=3D9018322866560060317) at
evm-db.c:1027
#7  0x0044b1d8 in evm_getVolLunList (evmTxn=3D0x2baf7c28) at =
evm-spm.c:459
#8  0x0044d378 in evm_procSpmRsp (mBuf=3D0x513bf0) at evm-spm.c:884
#9  0x00409f28 in evm_processMsg (mbuf=3D0x513bf0 "1\n",
sender=3D0x7f82db50)
    at evm-cfgd-rx.c:299
#10 0x00405884 in evm_rcvRmcMsg (sess=3D0x4d3cc0, mode=3D32768) at
evm-cfgd.c:594
#11 0x00405b7c in evm_processReceivedMessages (clockTick=3D0x7f82dd48)
    at evm-cfgd.c:640
#12 0x00406c38 in main (argc=3D1, argv=3D0x7f82ddc4, envp=3D0x7f82ddcc)
    at evm-cfgd.c:923



------_=_NextPart_001_01C8B6D9.65D34C48
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: ssc cores</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Update:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">You need to mount the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">unstr</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">i</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">pped</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">binaries =
and libraries on BSD as well. Raj just had a case when he could not get =
correct stack trace on BSD without mounting.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
10:06 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> John Keiffer; =
dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: ssc cores</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Yes, mount the build-tree =
paths on the filer and run the gdb as usual. The build tree directories =
have the libraries and binaries with all debug =
information.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> John Keiffer<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
10:04 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky; =
dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: ssc cores</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Okay. Are you saying that we =
should mount those paths directly on the filer, and then run GDB like we =
used to? Or are you saying we should mount those on a client and run =
some other command?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
10:01 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> John Keiffer; =
dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: ssc cores</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">The page describes what used =
to work on BSD. The compiler and gdb on linux is more recent revision =
(which does not always mean better), and based on what is happening it =
looks like it can&#8217;t get the stack trace right without all the =
debug information. So yes the page needs to be updated with what =
I&#8217;ve just described.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> John Keiffer<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
9:57 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky; =
dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: ssc cores</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">If we do a gdb directly on the =
filer for daemon core files, then why does it not work as it should? I =
believe that this is what everyone does in QA. Based on what you are =
saying it sounds like this process is not valid.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Does this page need to be modified?</FONT></SPAN><SPAN =
LANG=3D"en-us"> </SPAN><A =
HREF=3D"http://wiki.onstor.net/wiki/Coredump_and_crashdump#Daemon_core_fi=
le"><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://wiki.onstor.net/wiki/Coredump_and_crashdump#Daemon_=
core_file</FONT></U></SPAN><SPAN LANG=3D"en-us"></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">John</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
9:47 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky; =
dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: ssc cores</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Here is an example how to =
mount directories to get correct stacktrace:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050=
608-sub21/nfx-tree on /mnt type nfs =
(rw,addr=3D10.0.0.236)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050=
608-sub21/nfx-tree/Build/cg/opt/bin on /onstor/bin type nfs =
(rw,addr=3D10.0.0.236)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-050=
608-sub21/nfx-tree/Build/cg/opt/lib on /onstor/lib type nfs =
(rw,addr=3D10.0.0.236)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, May 13, 2008 =
9:40 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Software; dl-QA<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> ssc cores</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Hello,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">When you =
are trying to get the SSC core backtrace for a defect please remember to =
mount the libraries and binaries with the debugging information, =
otherwise the stack trace may be not quite right. See example =
below.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Max</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Here is =
what was reported in 21892:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#0&nbsp; =
0x2b5b5104 in kill () at ../string/bits/string2.h:998</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#1&nbsp; =
0x2b5b670c in *__GI_abort () at =
../sysdeps/generic/abort.c:88</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#2&nbsp; =
0x2b5f111c in __libc_message (do_abort=3D2, fmt=3D0x2b6c0878 &quot;*** =
glibc detected *** %s: 0x%s ***\n&quot;)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at =
../sysdeps/unix/sysv/linux/libc_fatal.c:145</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#3&nbsp; =
0x2b5f7e7c in malloc_printerr (action=3D3, str=3D0x2b6c0a4c =
&quot;malloc(): memory corruption&quot;, ptr=3D&lt;value optimized =
out&gt;) at malloc.c:5525</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#4&nbsp; =
0x2b5fa4a0 in _int_malloc (av=3D0x2b70eba0, bytes=3D&lt;value optimized =
out&gt;) at malloc.c:3933</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#5&nbsp; =
0x2b5fdd5c in __libc_calloc (n=3D&lt;value optimized out&gt;, =
elem_size=3D&lt;value optimized out&gt;) at =
malloc.c:3647</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#6&nbsp; =
0x0042e9d0 in evm_allocLunEntry ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#7&nbsp; =
0x0044b1d8 in evm_getVolLunList ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#8&nbsp; =
0x0044d378 in evm_procSpmRsp ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#9&nbsp; =
0x00409f28 in evm_processMsg ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#10 =
0x00405884 in evm_closeSess ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#11 =
0xffffffffffffff00 in ?? ()</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Correct =
stack trace looks like this:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#0&nbsp; =
0x2b5b5104 in kill () at ../string/bits/string2.h:998</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#1&nbsp; =
0x2b5b670c in *__GI_abort () at =
../sysdeps/generic/abort.c:88</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#2&nbsp; =
0x2b5f111c in __libc_message (do_abort=3D2, fmt=3D0x2b6c0878 =
&quot;&quot;)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at =
../sysdeps/unix/sysv/linux/libc_fatal.c:145</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#3&nbsp; =
0x2b5f7e7c in malloc_printerr (action=3D3, str=3D0x2b6c0a4c =
&quot;\n&quot;, </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; ptr=3D&lt;value optimized out&gt;) at =
malloc.c:5525</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#4&nbsp; =
0x2b5fa4a0 in _int_malloc (av=3D0x2b70eba0, bytes=3D&lt;value optimized =
out&gt;)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at malloc.c:3933</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#5&nbsp; =
0x2b5fdd5c in __libc_calloc (n=3D&lt;value optimized out&gt;, =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; elem_size=3D&lt;value optimized =
out&gt;) at malloc.c:3647</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#6&nbsp; =
0x0042e9d0 in evm_allocLunEntry (sid=3D9018322866560060317) at =
evm-db.c:1027</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#7&nbsp; =
0x0044b1d8 in evm_getVolLunList (evmTxn=3D0x2baf7c28) at =
evm-spm.c:459</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#8&nbsp; =
0x0044d378 in evm_procSpmRsp (mBuf=3D0x513bf0) at =
evm-spm.c:884</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#9&nbsp; =
0x00409f28 in evm_processMsg (mbuf=3D0x513bf0 &quot;1\n&quot;, =
sender=3D0x7f82db50)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at evm-cfgd-rx.c:299</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#10 =
0x00405884 in evm_rcvRmcMsg (sess=3D0x4d3cc0, mode=3D32768) at =
evm-cfgd.c:594</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#11 =
0x00405b7c in evm_processReceivedMessages =
(clockTick=3D0x7f82dd48)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at evm-cfgd.c:640</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">#12 =
0x00406c38 in main (argc=3D1, argv=3D0x7f82ddc4, =
envp=3D0x7f82ddcc)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp; at evm-cfgd.c:923</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C8B6D9.65D34C48--
