X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7A7BB.0FB64763@onstor-exch02.onstor.net>; Tue, 5 Jun 2007 14:47:06 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A7BB.0FB64763"
Content-class: urn:content-classes:message
Subject: malloc source code (Defect 19165)
Date: Tue, 5 Jun 2007 14:47:06 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E028FB481@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: malloc source code (Defect 19165)
Thread-Index: Acenuw+xhLjqBfVERU6P2DnV6LBz5Q==
From: "Mike Lee" <mike.lee@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>
Cc: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Raj Kumar" <raj.kumar@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

This is a multi-part message in MIME format.

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

Hi Andy and Larry:

I'm chasing after Defect 19165, where one of the SSC daemons crashed =
with the stack shown below.
I'm trying to figure out under what circumstance(s) malloc() would call =
wrterror() and abort() since it is not clear from the stack.  If it is =
due to memory exhaustion, then I like to figure out why malloc didn't =
just return NULL instead of aborting.

As such, I'm trying to find the source code for malloc.c, where the =
malloc() we used is compiled from.

Would you know where it may be?

Thanks.

-Mike

(gdb) where
#0  0x507abb34 in kill () at kill:2
#1  0x5082bc24 in abort ()
#2  0x5082ce1c in wrterror ()
#3  0x5082ebfc in malloc ()
#4  0x5082bf80 in calloc ()
#5  0x502e446c in rmc_alloc_msg (sz=3D24376) at rmc_api.c:1395
#6  0x502e5444 in rmc_get_msg (hdr=3D0x7ffff098) at rmc_api.c:1678
#7  0x502dad38 in rmc_internal_msgalloc (sess=3D0x1013fc00, =
msg=3D0x7ffff098, msg_alloc=3D0x502e53f4 <rmc_get_msg>) at rmc.c:1755
#8  0x502d67e4 in rmc_internal_getmsg (sess=3D0x10114338, =
msg_alloc=3D0x502e53f4 <rmc_get_msg>) at rmc.c:776
#9  0x502e2e5c in rmc_waitfor_msg (sess=3D0x10114000, msg=3D0x7ffff278, =
get_msgbuf=3D0x502e53f4 <rmc_get_msg>, timeout=3D0x7ffff270)
    at rmc_api.c:1017
#10 0x502e2974 in rmc_rpc (sess=3D0x10114000, req_buf=3D0x7ffff330, =
req_len=3D24, resp_buf=3D0x7ffff348, resp_len=3D0x7ffff2e0)
    at rmc_api.c:926
#11 0x489328 in sendRequestToFp (sess=3D0x10114000, timeout_sec=3D0, =
mid=3D9611, req=3D0x7ffff330, req_len=3D24, resp=3D0x7ffff348,
    resp_len=3D80) at ndmp-ssc-util.c:699
#12 0x453dbc in ndmp_sendGetStateReq (sess=3D0x10114000) at =
ndmp-data.c:3669
#13 0x4344e4 in ndmp_procSession (sess=3D0x10114000) at ndmp-main.c:3937
#14 0x42e3c4 in ndmp_acceptClient (serverFd=3D12) at ndmp-main.c:2490
#15 0x43009c in main (argc=3D1, argv=3D0x7ffffe64) at ndmp-main.c:2881
(gdb)          =20

------_=_NextPart_001_01C7A7BB.0FB64763
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>malloc source code (Defect 19165)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hi Andy and Larry:<BR>
<BR>
I'm chasing after Defect 19165, where one of the SSC daemons crashed =
with the stack shown below.<BR>
I'm trying to figure out under what circumstance(s) malloc() would call =
wrterror() and abort() since it is not clear from the stack.&nbsp; If it =
is due to memory exhaustion, then I like to figure out why malloc didn't =
just return NULL instead of aborting.<BR>
<BR>
As such, I'm trying to find the source code for malloc.c, where the =
malloc() we used is compiled from.<BR>
<BR>
Would you know where it may be?<BR>
<BR>
Thanks.<BR>
<BR>
-Mike<BR>
<BR>
(gdb) where<BR>
#0&nbsp; 0x507abb34 in kill () at kill:2<BR>
#1&nbsp; 0x5082bc24 in abort ()<BR>
#2&nbsp; 0x5082ce1c in wrterror ()<BR>
#3&nbsp; 0x5082ebfc in malloc ()<BR>
#4&nbsp; 0x5082bf80 in calloc ()<BR>
#5&nbsp; 0x502e446c in rmc_alloc_msg (sz=3D24376) at rmc_api.c:1395<BR>
#6&nbsp; 0x502e5444 in rmc_get_msg (hdr=3D0x7ffff098) at =
rmc_api.c:1678<BR>
#7&nbsp; 0x502dad38 in rmc_internal_msgalloc (sess=3D0x1013fc00, =
msg=3D0x7ffff098, msg_alloc=3D0x502e53f4 &lt;rmc_get_msg&gt;) at =
rmc.c:1755<BR>
#8&nbsp; 0x502d67e4 in rmc_internal_getmsg (sess=3D0x10114338, =
msg_alloc=3D0x502e53f4 &lt;rmc_get_msg&gt;) at rmc.c:776<BR>
#9&nbsp; 0x502e2e5c in rmc_waitfor_msg (sess=3D0x10114000, =
msg=3D0x7ffff278, get_msgbuf=3D0x502e53f4 &lt;rmc_get_msg&gt;, =
timeout=3D0x7ffff270)<BR>
&nbsp;&nbsp;&nbsp; at rmc_api.c:1017<BR>
#10 0x502e2974 in rmc_rpc (sess=3D0x10114000, req_buf=3D0x7ffff330, =
req_len=3D24, resp_buf=3D0x7ffff348, resp_len=3D0x7ffff2e0)<BR>
&nbsp;&nbsp;&nbsp; at rmc_api.c:926<BR>
#11 0x489328 in sendRequestToFp (sess=3D0x10114000, timeout_sec=3D0, =
mid=3D9611, req=3D0x7ffff330, req_len=3D24, resp=3D0x7ffff348,<BR>
&nbsp;&nbsp;&nbsp; resp_len=3D80) at ndmp-ssc-util.c:699<BR>
#12 0x453dbc in ndmp_sendGetStateReq (sess=3D0x10114000) at =
ndmp-data.c:3669<BR>
#13 0x4344e4 in ndmp_procSession (sess=3D0x10114000) at =
ndmp-main.c:3937<BR>
#14 0x42e3c4 in ndmp_acceptClient (serverFd=3D12) at =
ndmp-main.c:2490<BR>
#15 0x43009c in main (argc=3D1, argv=3D0x7ffffe64) at =
ndmp-main.c:2881<BR>
(gdb)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7A7BB.0FB64763--
