Prev: finding solution to 2 equations of 2 variables, not explicit
Next: Axis Image and positioning
From: Tom Blanpied on 29 Jul 2010 15:06
Hi,
I'm attempting to use a mex-file that has apparently been validated on the two versions of Matlab I use (2007a and 2010a). However, when I run it, I get the error listed below. (Similar in 2010a.)
I don't have the mex c code, so can't recompile. Is there anything else I can try to diagnose this? Both copies are student versions. Can this influence mex-file execution?
Thanks,
Tom
------------------------------------------------------------------------
Segmentation violation detected at Thu Jul 29 14:54:42 2010
------------------------------------------------------------------------
Configuration:
MATLAB Version: 7.4.0.287 (R2007a)
MATLAB License: STUDENT
Operating System: Microsoft Windows XP
Window System: Version 5.1 (Build 2600: Service Pack 3)
Processor ID: x86 Family 6 Model 7 Stepping 7, GenuineIntel
Virtual Machine: Java 1.5.0_07 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode
Default Charset: windows-1252
Register State:
EAX = 00031390 EBX = 190dfec8
ECX = 1a340030 EDX = ffffffff
ESI = 191f9b58 EDI = 00003139
EBP = 0000313a ESP = 00cec8d0
EIP = 15b61da9 FLG = 00010212
Stack Trace:
This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.
From: Rune Allnor on 29 Jul 2010 15:57
On 29 Jul, 21:06, "Tom Blanpied"
<tblanpied.butnotthisp...(a)verizon.net> wrote:
> Hi,
> I'm attempting to use a mex-file that has apparently been validated on the two versions of Matlab I use (2007a and 2010a). However, when I run it, I get the error listed below. (Similar in 2010a.)
> I don't have the mex c code, so can't recompile. Is there anything else I can try to diagnose this?

The diagnosis is there: A segmentation error. That's a *bad*
error, which you need the source code to correct. The code is
attempting to access a section of memory it is not supposed to.
Depending on if it reads or writes, it might have corrupted
memory used by other programs.

Contact the author of the code. Don't use it till it have
been fixed.

Rune
 | 
Pages: 1
Prev: finding solution to 2 equations of 2 variables, not explicit
Next: Axis Image and positioning