From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Mex file from codegen seg faulting
Date: Fri, 7 Dec 2012 21:17:14 +0000 (UTC)
Organization: Rincon Research Corp
Lines: 8
Message-ID: <k9tmcq$r3f$>
References: <k9tg40$3a1$>
Reply-To: <HIDDEN>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: 1354915034 27759 (7 Dec 2012 21:17:14 GMT)
NNTP-Posting-Date: Fri, 7 Dec 2012 21:17:14 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 2235717
Xref: comp.soft-sys.matlab:784413

"Chuck37" wrote in message <k9tg40$3a1$>...
> I have a mex file that I generated from Matlab using codegen.  It worked fine for a long time but recently it has been seg faulting.  The seg faults are improbable, but will always happen within 100 runs.  Is there some sort of debugging I can turn on to catch the error, to isolate it to a line of code or something?
> Making this more difficult is the fact the with codegen integrity checks on, the code is unusable due to being so slow.  It takes many minutes where the plain old matlab will run in seconds.  Not sure what that means, but I expect it'll make it harder to find this problem.
> Any ideas would be great. 

Okay, I thought I knew which mex this was, but it looks like its happening in any one of three randomly.  How could that be?  I notice the crash dump files have "crash decoding: disabled".  Would that be of value, and if so how do you enable it?