AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090215155909.0870f732@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>,<ed.kwan@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB51851F492B6@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Sun, 15 Feb 2009 15:59:25 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Jonathan Goldick <jonathan.goldick@onstor.com>
Cc: Ed Kwan <ed.kwan@onstor.com>, Maxim Kozlovsky
 <maxim.kozlovsky@onstor.com>
Subject: Re: Defect  TED00026229 Daemon sdm_cfgd restarted and produced core
 file - request for analysis - customer Bevan Howard - case 11524
Message-ID: <20090215155925.1c9e0068@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB51851F492B6@exch1.onstor.net>
References: <71a4fef2-f14d-4a35-a089-e9af5354629f@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851F4925F@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851F4926A@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851F4926B@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851F4929D@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB51851F492B6@exch1.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

Yes, I believe that's always turned on, and we even mucked with it on
Linux to get it to do the same thing.  It does an abort so we get a
core file.


On Thu, 12 Feb 2009 15:16:26 -0800 Jonathan Goldick
<jonathan.goldick@onstor.com> wrote:

> Thanks.  I'm done with it, not that there was much I could find.  We
> don't know what malloc error was being reported.
> 
> From a reading of our openbsd malloc.c source code I only see us
> crashing this way if we ran out of memory and someone enabled the -X
> option which causes this type of behavior.  I seem to remember Max
> talking about doing that but don't remember if this version of code
> has it.
> 
> Given that the core is 17MB it seems plausible that we ran out of
> memory somehow.
> 
> 
> -----Original Message-----
> From: Ed Kwan 
> Sent: Thursday, February 12, 2009 2:54 PM
> To: Jonathan Goldick
> Subject: RE: Defect TED00026229 Daemon sdm_cfgd restarted and
> produced core file - request for analysis - customer Bevan Howard -
> case 11524
> 
> I've copied the core file to eng236.onstor.lab.
> 
> eng236# scp
> edk@10.0.0.137://n/dw_rw_bycase/case0010001-case0012000/case11567/onstorCH0,sn_0711051009/system_get_all,20090205_23270359/cores/sdm_cfgd.core /
> edk@10.0.0.137's password:
> sdm_cfgd.core                                             100%   17MB
> 438.7KB/s   00:40
> 
> eng236#
> gdb  /bt/R3.3.2.0/R3.3.2.0-GA/nfx-tree/Build/bc/opt/bin/sdm_cfgd /sdm_cfgd.core
> (gdb) bt #0  0x5074bb34 in kill () at kill:2
> #1  0x507cbc24 in abort ()
> #2  0x507cce1c in wrterror ()
> #3  0x507cebfc in malloc ()
> #4  0x507cbf80 in calloc ()
> #5  0x5025ac38 in rmc_init_sess_msg_qs (sess=0x11085400) at rmc.c:2057
> #6  0x5025a468 in rmc_internal_acpt (sess=0x10254400, msg=0x7ffffb78,
> new_sess=0x7ffffc0c) at rmc.c:1915
> #7  0x50256f24 in rmc_internal_getmsg (sess=0x10254400,
>     msg_alloc=0x4479c8 <sdm_allocRmcMsg>) at rmc.c:1084
> #8  0x50266224 in rmc_get_completed_msg (sess=0x10254400,
> msg=0x7ffffccc, msg_alloc_func=0x4479c8 <sdm_allocRmcMsg>, mode=0) at
> rmc_api.c:1795 #9  0x44a2ac in sdm_rcvRmcMsg (sess=0x10254400,
> mode=0) at sdm-msg.c:1299 #10 0x45dc60 in sdm_rcvMsg () at
> sdm-msg.c:7037 #11 0x413300 in main () at sdm-main.c:274
