Prev: Calculations involving Sparse Matrix
Next: likelihood estimates of glmfit results?
From: Jamal Mohamed on 6 Jan 2010 03:53
hi
how to set up in my system to create mex-files and to compile C-mex in my system.
when i typed the following commend in commend window

I = imread('C:\lena.jpg');
h = daubcqf (4, 'min');
L = 1;
[y,L] = mdwt(I, h, L);

this code from rice wavelet toolbox.
even i had tried to mex -setup.

The following information came there. please instruct me what i do next...
please i want immediate reply from you.

=======error message========

Saving minidump to file C:\Users\User\AppData\Local\Temp\matlab_crash_dump.5224.0.dmp

------------------------------------------------------------------------
Segmentation violation detected at Wed Jan 06 11:13:54 2010
------------------------------------------------------------------------

Configuration:
MATLAB Version: 7.6.0.324 (R2008a)
MATLAB License: 161051
Operating System: Microsoft Windows Vista
Window System: Version 6.0 (Build 6002: Service Pack 2)
Processor ID: x86 Family 6 Model 7 Stepping 10, GenuineIntel
Virtual Machine: Java 1.6.0 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode
Default Encoding: windows-1252

Fault Count: 1

Register State:
EAX = 00004000 EBX = 1bc61030
ECX = 00000150 EDX = 1ae85d20
ESI = ea240000 EDI = 00000200
EBP = 00d3e4a8 ESP = 00d3e440
EIP = 05ee1627 FLG = 00210246

Stack Trace:
[0] mdwt.mexw32:0x05ee1627(0x05de0030 "ÞÞàáâáâáààáâããäçàâàÝÞâåäáßßáâââã..", 512, 768, 0x197781e0)
[1] mdwt.mexw32:0x05ee119f(2, 0x00d3eb2c, 1, 0x00d3eb8c)
[2] libmex.dll:_mexRunMexFile(2, 0x00d3eb2c, 3, 0x00d3eb8c) + 129 bytes
[3] libmex.dll:private: void __thiscall Mfh_mex::runMexFileWithSignalProtection(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(2, 0x00d3eb2c, 3, 0x00d3eb8c) + 73 bytes
[4] libmex.dll:public: virtual void __thiscall Mfh_mex::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(2, 0x00d3eb2c, 3, 0x00d3eb8c) + 220 bytes
[5] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(2, 0x00d3eb2c, 3, 0x00d3eb8c) + 193 bytes
[6] m_interpreter.dll:__catch$?inDispatchFromStack@@YAHHPBDHH@Z$0(794, 0x1977202c "mdwt", 2, 3) + 712 bytes
[7] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const *,int,int,int,int *,int *)(0x1977202c "mdwt", 794, 2, 3) + 146 bytes
[8] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *,int *)(1, 0, 1, 0) + 2898 bytes
[9] m_interpreter.dll:int __cdecl protected_inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0, 1, 0) + 74 bytes
[10] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0, 1, 0) + 254 bytes
[11] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class Mfh_mp *,bool)(0x05ec86e0, 0x05ec8601, 0xffffffff, 0x05ec86e0) + 1330 bytes
[12] m_interpreter.dll:void __cdecl inRunMfile(int,struct mxArray_tag * *,int,struct mxArray_tag * *,class Mfh_mp *,struct inWorkSpace_tag *)(0, 0x00d3f394, 0, 0) + 679 bytes
[13] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0, 0x00d3f394, 0) + 29 bytes
[14] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00d3f394, 0, 0) + 28 bytes
[15] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00d3f394, 0, 0) + 193 bytes
[16] m_interpreter.dll:void __cdecl inEvalPcodeHeaderToWord(struct _memory_context *,int,struct mxArray_tag * * const,struct _pcodeheader *,class Mfh_mp *,unsigned long)(0x7ad2e5e4, 0, 0x00d3f394, 0x00d3f250) + 201 bytes
[17] m_interpreter.dll:enum inExecutionStatus __cdecl in_local_call_script_function(struct _memory_context *,struct _pcodeheader *,int,struct mxArray_tag * * const,unsigned long,bool)(0x7ad2e5e4, 0x00d3f250, 0, 0x00d3f394) + 91 bytes
[18] m_interpreter.dll:enum inExecutionStatus __cdecl inEvalStringWithIsVarFcn(struct _memory_context *,char const *,enum EvalType,int,struct mxArray_tag * * const,enum inDebugCheck,struct _pcodeheader *,int *,bool (__cdecl*)(void *,char const *),void *,bool,bool)(0x7ad2e5e4, 0x19800020 "[y,L] = mdwt(I,h,L);\n", 0, 0) + 570 bytes
[19] m_interpreter.dll:enum inExecutionStatus __cdecl inEvalCmdWithLocalReturn(char const *,int *,bool,bool,bool (__cdecl*)(void *,char const *))(0x19800020 "[y,L] = mdwt(I,h,L);\n", 0, 1, 0x79cad700) + 97 bytes
[20] m_interpreter.dll:_inEvalCmdWithLocalReturn(0x19800020 "[y,L] = mdwt(I,h,L);\n", 0, 0, 1) + 28 bytes
[21] bridge.dll:enum inExecutionStatus __cdecl evalCommandWithLongjmpSafety(char const *)(0x19800020 "[y,L] = mdwt(I,h,L);\n", 0x01b9de18, 0x017b2a90, 0x01b9de18) + 67 bytes
[22] bridge.dll:__catch$_mnParser$0(0x01b9de18, 0x06a095e0, 0x79730101, 0x069b63f0) + 294 bytes
[23] mcr.dll:public: void __thiscall mcrInstance::mnParser(void)(0x004043ec, 795222, 0, 0x505c3a43) + 51 bytes
[24] MATLAB.exe:_WinMain(a)16(0x017b2a90, 0, 795222, 0x01b9de18) + 405 bytes
[25] MATLAB.exe:___tmainCRTStartup(0x7ffd8000, 0x00d3ffd4 "ìÿÓ", 0x77b819bb, 0x7ffd8000) + 320 bytes
[26] kernel32.dll:0x7675d0e9(0x7ffd8000, 0x7712e628, 0, 0)
[27] ntdll.dll:0x77b819bb(0x00401943, 0x7ffd8000, 0, 0)
[28] ntdll.dll:0x77b8198e(0x00401943, 0x7ffd8000, 0, 48)

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.

If it is an official MathWorks function, please
follow these steps to report this problem to The MathWorks so we
have the best chance of correcting it:

The next time MATLAB is launched under typical usage, a dialog box will
open to help you send the error log to The MathWorks. Alternatively, you
can send an e-mail to segv(a)mathworks.com with the following file attached:
C:\Users\User\AppData\Local\Temp\matlab_crash_dump.5224

If the problem is reproducible, please submit a Service Request via:
http://www.mathworks.com/support/contact_us/ts/help_request_1.html

A technical support engineer might contact you with further information.

Thank you for your help. MATLAB may attempt to recover, but even if recovery appears successful,
we recommend that you save your workspace and restart MATLAB as soon as possible.
From: Jan Simon on 6 Jan 2010 07:19
Dear Jamal!

> how to set up in my system to create mex-files and to compile C-mex in my system.
> when i typed the following commend in commend window
>
> I = imread('C:\lena.jpg');
> h = daubcqf (4, 'min');
> L = 1;
> [y,L] = mdwt(I, h, L);
>
> this code from rice wavelet toolbox.
> even i had tried to mex -setup.

"mex -setup" and an error from the MEX file are two distinct things! There is no relation. Therefore I please you to describe, when the error appears and if the corresponding function has ever worked.

Kind regards, Jan
From: Jamal Mohamed on 6 Jan 2010 07:56
thank u for reply. yeah correct. but no one c file not work out. for example
"mex yprime.c

C:\PROGRA~1\MATLAB\R2008A\BIN\MEX.PL: Error: 'yprime.c' not found.

??? Error using ==> mex at 207
Unable to complete successfully."

please watch it "error message" too. then i think that u will catch this problem

"Jan Simon" <matlab.THIS_YEAR(a)nMINUSsimon.de> wrote in message <hi1v3r$iom$1(a)fred.mathworks.com>...
> Dear Jamal!
>
> > how to set up in my system to create mex-files and to compile C-mex in my system.
> > when i typed the following commend in commend window
> >
> > I = imread('C:\lena.jpg');
> > h = daubcqf (4, 'min');
> > L = 1;
> > [y,L] = mdwt(I, h, L);
> >
> > this code from rice wavelet toolbox.
> > even i had tried to mex -setup.
>
> "mex -setup" and an error from the MEX file are two distinct things! There is no relation. Therefore I please you to describe, when the error appears and if the corresponding function has ever worked.
>
> Kind regards, Jan
From: Praetorian on 6 Jan 2010 09:20
On Jan 6, 5:56 am, "Jamal Mohamed" <in.ja...(a)yahoo.com> wrote:
> thank u for reply. yeah correct. but no one c file not work out. for example
>  "mex yprime.c
>
>   C:\PROGRA~1\MATLAB\R2008A\BIN\MEX.PL: Error: 'yprime.c' not found.
>
> ??? Error using ==> mex at 207
> Unable to complete successfully."
>
> please watch it "error message" too. then i think that u will catch this problem
>
> "Jan Simon" <matlab.THIS_Y...(a)nMINUSsimon.de> wrote in message <hi1v3r$io....(a)fred.mathworks.com>...
> > Dear Jamal!
>
> > >  how to set up in my system to create mex-files and to compile C-mex in my system.
> > > when i typed the following commend in commend window
>
> > > I = imread('C:\lena.jpg');
> > > h = daubcqf (4, 'min');
> > > L = 1;
> > > [y,L] = mdwt(I, h, L);
>
> > > this code from rice wavelet toolbox.
> > > even i had tried to mex -setup.
>
> > "mex -setup" and an error from the MEX file are two distinct things! There is no relation. Therefore I please you to describe, when the error appears and if the corresponding function has ever worked.
>
> > Kind regards, Jan

Jamal,
Does yprime.c exist in the current working directory when you run the
MEX command? Note that the MEX command does not search the MATLAB path
and must be supplied with an absolute or relative path to the source
file if it is not in the current directory. The PWD command will
return the path of the current directory.

HTH,
Ashish.
 | 
Pages: 1
Prev: Calculations involving Sparse Matrix
Next: likelihood estimates of glmfit results?