Path: news.mathworks.com!newsfeed-00.mathworks.com!newsfeed2.dallas1.level3.net!news.level3.com!postnews.google.com!news1.google.com!news.glorb.com!news2.glorb.com!tr22g12.aset.psu.edu!news.mathforum.org!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Segmentation violation due to MEX code
Date: Mon, 06 Jul 2009 09:34:17 EDT
Organization: The Math Forum
Lines: 9
Message-ID: <28112995.79623.1246887287751.JavaMail.jakarta@nitrogen.mathforum.org>
References: <1861877.79321.1246884234900.JavaMail.jakarta@nitrogen.mathforum.org>
NNTP-Posting-Host: nitrogen.mathforum.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: support1.mathforum.org 1246887287 25887 144.118.30.135 (6 Jul 2009 13:34:47 GMT)
X-Complaints-To: news@news.mathforum.org
NNTP-Posting-Date: Mon, 6 Jul 2009 13:34:47 +0000 (UTC)
Xref: news.mathworks.com comp.soft-sys.matlab:553080


I am pretty sure the problem has to do with memory allocation when calling the function.

I think so because I have tried to make it work with arrays with up to 4000 values and it performs correctly...

Any idea if what I say makes sense?

If so, how can I increase the memory assigned to the MEX function?

Thanks!