Discussion :

[vanesima]

salut à tous,
bon je saute sur l'occasion pour poser la question sur les mex files.
en fait j'ai des programmes en C je les exécutés sous matlab, mais quand je les ai modifiés et relancés ca m'a posé un problème au niveau de l'éxécution de mex.
à votre avis ou se situe le problème?? je suis vraiment bloquée et je n'arrive pas à modifier les programmes C pour avancer.

[Jerome Briot]

Sans les messages d'erreur ou plus d'informations, ce sera très difficile de te répondre

[vanesima]

Sans les messages d'erreur ou plus d'informations, ce sera très difficile de te répondre

bonjour Dut;
à partir de l'excusion des programmes C sous matlab voila ce qu'il m'affiche, j'ai dû comprendre que je suis en train de violer l'utilisation du programme, parceque je l'ai récupéré, pourtant l'auteur a donné sa permission de l'utiliser et il a donné meme ce qu'il faut faire pour pouvoir le modifier ??? mais ca marche pas

-----------------------------------------------------------------------
Segmentation violation detected at Mon Oct 29 08:58:07 2007
-----------------------------------------------------------------------
Configuration:
MATLAB Version: 7.0.0.19920 (R14)
Operating System: Microsoft Windows XP
Window System: Version 5.1 (Build 2600: Service Pack 2)
Processor ID: x86 Family 15 Model 4 Stepping 10, GenuineIntel
Virtual Machine: Java 1.4.2 with Sun Microsystems Inc. Java HotSpot(TM) Client VM
(mixed mode)
Default Charset: ibm-5348_P100-1997
Register State:
EAX = 00000000 EBX = 12201f80
ECX = 121b8fd8 EDX = 12170030
ESI = 00000100 EDI = 12e000ac
EBP = 00cdc6b4 ESP = 00cdc684
EIP = 0fad155a FLG = 00210293
Stack Trace:
[0] elim_redon.dll:0x0fad155a(0x12170030, 298920, 0x12a90004 "ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ..", 0x00cdd300)
[1] elim_redon.dll:0x0fad1381(1, 0x00cdd300, 1, 0x00cdd390)
[2] libmex.dll:_mexRunMexFile(1, 0x00cdd300, 1, 0x00cdd390) + 71 bytes
[3] libmex.dll:public: virtual void __thiscall Mfh_mex::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(1, 0x00cdd300, 1, 0x00cdd390) + 157 bytes
[4] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(1, 0x00cdd300, 1, 0x00cdd390) + 273 bytes
[5] m_interpreter.dll:public: void __thiscall ResolverFunctionDesc::CallFunction(int,struct mxArray_tag * * const,int,struct mxArray_tag * * const)(1, 0x00cdd300, 1, 0x00cdd390) + 246 bytes
[6] m_interpreter.dll:public: bool __thiscall Resolver::CallMFunction(int,int,class _m_operand * const,union m_operand_storage *,int,class _m_operand * const,union m_operand_storage *,int *)(1, 1, 0x116ad750, 0) + 840 bytes
[7] m_interpreter.dll:bool __cdecl inResolveMFunctionCall(struct _m_function_desc *,int,int,class _m_operand * const,union m_operand_storage *,int,class _m_operand * const,union m_operand_storage *,int *,enum inMarshalType *,unsigned int,int,unsigned int *,int)(0x1181d220, 1, 1, 0x116ad750) + 148 bytes
[8] m_interpreter.dll:bool __cdecl accelMFunctionCall(struct _accelOp *,struct _accelOp * *,struct _accelBytecode *,int *,enum inMarshalType *)(0x112d7220, 0x00cdd9a4, 0x11599d10, 0x00cdd99c) + 108 bytes
[9] m_interpreter.dll:int __cdecl accelExec(struct _accelBytecode *,enum inMarshalType *)(0x11599d10, 0x00cdda1c, 0, 0) + 18462 bytes
[10] m_interpreter.dll:_inExecuteHotSegment(0x00cdda50, 0x00cddb20, 0x00cddad0, 0) + 1542 bytes
[11] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(1, 611, 45, 0) + 365 bytes
[12] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(1, 611, 26, 0) + 272 bytes
[13] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class Mfh_mp *,bool)(0x10961c60, 0, 3, 3) + 773 bytes
[14] m_interpreter.dll:_inWordsj(1, 0x00cde03c, 3, 0x00cde09c) + 441 bytes
[15] m_interpreter.dll:public: void __thiscall Mfh_mp::inRunMP(int,struct mxArray_tag * *,int,struct mxArray_tag * *,struct inWorkSpace_tag *)(1, 0x00cde03c, 3, 0x00cde09c) + 158 bytes
[16] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 1, 0x00cde03c, 3) + 28 bytes
[17] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(1, 0x00cde03c, 3, 0x00cde09c) + 26 bytes
[18] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(1, 0x00cde03c, 3, 0x00cde09c) + 273 bytes
[19] m_interpreter.dll:_inDispatchFromStack(595, 0x10719837 "f_seg", 1, 3) + 891 bytes
[20] m_interpreter.dll:_inCallFcnFromReference(0, 0x11625f50, 0x789b59c0, 0xcccccccd) + 176 bytes
[21] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(1, 0, 29, 0) + 4115 bytes
[22] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(1, 0, 2, 0) + 272 bytes
[23] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class Mfh_mp *,bool)(0x105277a0, 1, 0, 0x105277a0) + 773 bytes
[24] m_interpreter.dll:_inExecCompScript(0, 0x00cde71c, 0x105277a0, 0xffffffff) + 321 bytes
[25] m_interpreter.dll:public: void __thiscall Mfh_mp::inRunMP(int,struct mxArray_tag * *,int,struct mxArray_tag * *,struct inWorkSpace_tag *)(0, 0x00cde71c, 0, 0x00cde77c) + 122 bytes
[26] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0, 0x00cde71c, 0) + 28 bytes
[27] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cde71c, 0, 0x00cde77c) + 26 bytes
[28] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cde71c, 0, 0x00cde77c) + 273 bytes
[29] m_interpreter.dll:_inDispatchFromStack(484, 0x013ea414 "main", 0, 0) + 891 bytes
[30] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const *,int,int,int,int *,int *)(0x013ea414 "main", 484, 0, 0) + 111 bytes
[31] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(2, 0, 0, 0) + 2411 bytes
[32] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(2, 0, 0, 0) + 272 bytes
[33] m_interpreter.dll:_inInterPcode(2, 0x7876f2d8 "¸òvx°úrx`ûrxÐúrx¸òvxØòvx", 0, 0) + 69 bytes
[34] m_interpreter.dll:enum inExecutionStatus __cdecl in_local_call_eval_function(int *,struct _pcodeheader *,int *,struct mxArray_tag * * const,enum inDebugCheck)(0x00cdf2c8, 0x00cdf3bc, 2, 0x10753a90 "main\n") + 162 bytes
[35] m_interpreter.dll:$L72592(0x7876f2d8 "¸òvx°úrx`ûrxÐúrx¸òvxØòvx", 0x10753a90 "main\n", 5, 0) + 196 bytes
[36] m_interpreter.dll:enum inExecutionStatus __cdecl inEvalCmdWithLocalReturnandtype(char const *,int *,enum inDebugCheck)(0, 2, 1, 0x00cdf44c "ôôÍ") + 86 bytes
[37] m_interpreter.dll:_inEvalCmdNoEnd(0x10753a90 "main\n", 0x00cdf4e4, 0x00cdf4a0, 0x015b2180) + 16 bytes
[38] bridge.dll:_mnParser(0x7c80b6a1, 0x015b2180, 0, 0) + 431 bytes
[39] mcr.dll:public: void __thiscall mcrInstance::mnParser(void)(271242, 0x4d5c3a43, 0x414c5441, 0x625c3742) + 87 bytes
[40] MATLAB.exe:0x00401d2f(4194304, 0, 271242, 0x015b2180)
[41] MATLAB.exe:0x00403e45(3342387, 3145779, 0x7ffdb000, 0x8054a6ed)
[42] kernel32.dll:0x7c816fd7(0x00403cc0 "jth(U@", 0, 0, 1245343)
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 in reporting this problem to The MathWorks so
that we have the best chance of correcting it:
1. Send this crash report to segv@mathworks.com for automated analysis.
For your convenience, this information has been recorded in:
C:\DOCUME~1\WINDOWS\LOCALS~1\Temp\matlab_crash_dump.1432
2. Also, if the problem is reproducible, send the crash report to
support@mathworks.com along with:
- A specific list of steps that will reproduce the problem
- Any M, MEX, MDL or other files required to reproduce the problem
- Any error messages displayed to the command window
A technical support engineer will contact you with further information.
Thank you for your assistance. Please save your workspace and restart
MATLAB before continuing your work.
==============================================================

[tug83]

en quelle version cette dll fonctionnait tu le sait?
Là d'apres le crash on voit que tu l'utilises en R14.
Il se peut qu'il faille la recompiler si elle a été faite en R13 par exemple.

[vanesima]

en quelle version cette dll fonctionnait tu le sait?
Là d'apres le crash on voit que tu l'utilises en R14.
Il se peut qu'il faille la recompiler si elle a été faite en R13 par exemple.

aparament c'est ca. mais avant d'exécuter j'ai recompilé les programmes suivant les indications de l'auteur