Erreur Segmentation Violation

**rv29634** · 25/11/2007, 08h47

Bonjour,

J'utilise Matlab sous Linux.
La version est: 7.4.0.336 (R2007a)

Lors de l'execution d'un mex file j'ai le message d'erreur suivant:

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
 
------------------------------------------------------------------------
       Segmentation violation detected at Sun Nov 25 01:58:36 2007
------------------------------------------------------------------------
 
Configuration:
  MATLAB Version:   7.4.0.336 (R2007a)
  MATLAB License:   xxxxxx
  Operating System: Linux 2.6.22.9-91.fc7.stk16 #1 SMP Mon Oct 1 18:06:09 EDT 2007 i686
  GNU C Library:    2.6 stable
  Window System:    The X.Org Foundation (10300000), display :0.0
  Current Visual:   0x23 (class 4, depth 24)
  Processor ID:     x86 Family 6 Model 14 Stepping 12, GenuineIntel
  Virtual Machine:  Java 1.5.0 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode
  Default Charset:  UTF-8
 
Register State:
  eax = 00000000   ebx = 002b5528
  ecx = a1f40ef0   edx = 00000000
  esi = 00000000   edi = bfda549c
  ebp = bfda4bb8   esp = bfda4bb0
  eip = 00283107   flg = 00010216
 
Stack Trace:
  [0] libmx.so:mxgetm_@@v7.3(0xbfda549c, 0, 0xa22622f0, 0) + 23 bytes
  [1] heatsnk.mexglx:mexfunction_~(0xbfda4d20, 0xbfda549c, 0xbfda4d28, 0xbfda54fc) + 178 bytes
  [2] libmex.so:mexRunMexFile(1, 0xbfda549c, 1, 0xbfda54fc) + 137 bytes
  [3] libmex.so:Mfh_mex::runMexFileWithSignalProtection(int, mxArray_tag**, int, mxArray_tag**)(0xa2dc1070, 1, 0xbfda549c, 1) + 173 bytes
  [4] libmex.so:Mfh_mex::dispatch_file(int, mxArray_tag**, int, mxArray_tag**)(0xa2dc1070, 1, 0xbfda549c, 1) + 251 bytes
  [5] libmwm_dispatcher.so:Mfh_file::dispatch_fh(int, mxArray_tag**, int, mxArray_tag**)(0xa2dc1070, 1, 0xbfda549c, 1) + 217 bytes
  [6] libmwm_interpreter.so:inDispatchWithDebug(0xbfda549c, 1, 0xbfda54fc, 0) + 436 bytes
  [7] libmwm_interpreter.so:inDispatchFromStack(730, 0xa2dc54b0 "heatsnk", 1, 1) + 1400 bytes
  [8] libmwm_interpreter.so:inDispatchCall(char const*, int, int, int, int*, int*)(1, 0xbfda57e8, 0xa2dc54a4, 0) + 160 bytes
  [9] libmwm_interpreter.so:.L694(2, 0, 0, 0) + 165 bytes
  [10] libmwm_interpreter.so:protected_inInterp(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, int*)(2, 0, 0, 0) + 112 bytes
  [11] libmwm_interpreter.so:inInterPcodeSJ(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, int*)(0, 0xa22cd340, 0xbfda5bd0, 0xbfda5c8c) + 318 bytes
  [12] libmwm_interpreter.so:inInterPcode(2, 0, 0x00511460, 0x00510a40) + 113 bytes
  [13] libmwm_interpreter.so:inEvalStringWithIsVarFcn(_memory_context*, char const*, EvalType, int, mxArray_tag**, inDebugCheck, _pcodeheader*, int*, bool (*)(void*, char const*), void*)(1901864, 0x08d896c0 "y=heatsnk(x)\n", 0, 0) + 4149 bytes
  [14] libmwm_interpreter.so:inEvalCmdNoEnd(0x08d896c0 "y=heatsnk(x)\n", 1, 0xbfda6728, 1437806) + 126 bytes
  [15] libmwbridge.so:ThrowSignal(char const*)(0x08d896c0 "y=heatsnk(x)\n", 2, 0xbfda6890, 0x00424360) + 145 bytes
  [16] libmwbridge.so:mnParser(0xbfda6914, 0x08100ce8, 1, 0x0045bf12) + 277 bytes
  [17] libmwmcr.so:mcrInstance::mnParser()(0x08100ce8, 0xbfda8ba8, 0x08100cd8, 0x08100d20) + 52 bytes
 
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@mathworks.com with the following file attached:
    /home/remi/matlab_crash_dump.3289
 
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. Save your workspace and restart MATLAB.

Avez vous une idée de ce que cela signifie ?

**paradize3** · 26/11/2007, 11h15

qu'il y a un bug dans ton mex file, c'est toi qui l'a écrit? Si tu peux poster on pourra jeter un coup d'oeil.

En attendant tu peux aller lire ca: http://www.mathworks.com/company/new...iolations.html

Salutations,

Gregoire

**rv29634** · 26/11/2007, 16h27

Oui j'ai écrit ce mex file pour interfacer du code Fortran avec Matlab.
Le mex file est plutôt long... Celui-ci ayant évolué depuis mon précédent post je reposte le message d'erreur.

Message d'erreur:

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
 
------------------------------------------------------------------------
       Segmentation violation detected at Mon Nov 26 10:17:44 2007
------------------------------------------------------------------------
 
Configuration:
  MATLAB Version:   7.4.0.336 (R2007a)
  MATLAB License:   xxxxxx
  Operating System: Linux 2.6.22.9-91.fc7.stk16 #1 SMP Mon Oct 1 18:06:09 EDT 2007 i686
  GNU C Library:    2.6 stable
  Window System:    The X.Org Foundation (10300000), display :0.0
  Current Visual:   0x23 (class 4, depth 24)
  Processor ID:     x86 Family 6 Model 14 Stepping 12, GenuineIntel
  Virtual Machine:  Java 1.5.0 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode
  Default Charset:  UTF-8
 
Register State:
  eax = 00001a44   ebx = 03e01274
  ecx = 000000aa   edx = 03e3a300
  esi = 00000001   edi = 03e01be0
  ebp = bf9c0cd8   esp = bf9c0af0
  eip = 03dfc354   flg = 00010287
 
Stack Trace:
  [0] analysis.mexglx:0x03dfc354(0xbf9c0f54, 0xbf9c1014, 0xbf9c0f54, 0x3fd99999)
  [1] analysis.mexglx:0x03dfeebf(0xbf9c0fd0, 0xbf9c1014, 0xbf9c106c, 0xbf9c1010)
  [2] analysis.mexglx:0x03dff17d(0xbf9c0fd0, 0xbf9c1014, 0xbf9c106c, 0xbf9c1010)
  [3] analysis.mexglx:0x03dff201(0xbf9c10a0, 0xbf9c10d4, 0xbf9c10c0, 0xbf9c10dc)
  [4] analysis.mexglx:mexfunction_~(0xbf9c1140, 0xbf9c18bc, 0xbf9c1148, 0xbf9c191c) + 385 bytes
  [5] libmex.so:mexRunMexFile(4, 0xbf9c18bc, 2, 0xbf9c191c) + 137 bytes
  [6] libmex.so:Mfh_mex::runMexFileWithSignalProtection(int, mxArray_tag**, int, mxArray_tag**)(0xa374f2b0, 4, 0xbf9c18bc, 2) + 173 bytes
  [7] libmex.so:Mfh_mex::dispatch_file(int, mxArray_tag**, int, mxArray_tag**)(0xa374f2b0, 4, 0xbf9c18bc, 2) + 251 bytes
  [8] libmwm_dispatcher.so:Mfh_file::dispatch_fh(int, mxArray_tag**, int, mxArray_tag**)(0xa374f2b0, 4, 0xbf9c18bc, 2) + 217 bytes
  [9] libmwm_interpreter.so:inDispatchWithDebug(0xbf9c18bc, 2, 0xbf9c191c, 0) + 436 bytes
  [10] libmwm_interpreter.so:inDispatchFromStack(695, 0x08eb199c "analysis", 4, 2) + 1400 bytes
  [11] libmwm_interpreter.so:inDispatchCall(char const*, int, int, int, int*, int*)(2, 0xbf9c1c08, 0x08eb1990, 0) + 160 bytes
  [12] libmwm_interpreter.so:.L694(2, 0, 0, 0) + 165 bytes
  [13] libmwm_interpreter.so:protected_inInterp(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, int*)(2, 0, 0, 0) + 112 bytes
  [14] libmwm_interpreter.so:inInterPcodeSJ(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, int*)(0, 0xa28deb80, 0xbf9c1ff0, 0xbf9c20ac) + 318 bytes
  [15] libmwm_interpreter.so:inInterPcode(2, 0, 0x00511460, 0x00510a40) + 113 bytes
  [16] libmwm_interpreter.so:inEvalStringWithIsVarFcn(_memory_context*, char const*, EvalType, int, mxArray_tag**, inDebugCheck, _pcodeheader*, int*, bool (*)(void*, char const*), void*)(1901864, 0x08da16b0 "[y obj g ncall]=analysis(x,ncall..", 0, 0) + 4149 bytes
  [17] libmwm_interpreter.so:inEvalCmdNoEnd(0x08da16b0 "[y obj g ncall]=analysis(x,ncall..", 1, 0xbf9c2b48, 1604113) + 126 bytes
  [18] libmwbridge.so:ThrowSignal(char const*)(0x08da16b0 "[y obj g ncall]=analysis(x,ncall..", 1, 0xbf9c2cb0, 0x00424360) + 145 bytes
  [19] libmwbridge.so:mnParser(0xbf9c2d34, 0x087f4d48, 1, 0x0045bf12) + 277 bytes
  [20] libmwmcr.so:mcrInstance::mnParser()(0x087f4d48, 0xbf9c4fc8, 0x087f4d38, 0x087f4d80) + 52 bytes
 
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@mathworks.com with the following file attached:
    /home/remi/matlab_crash_dump.3523
 
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. Save your workspace and restart MATLAB.

Le code source du Mex file est attaché (trop long pour pouvoir être collé dans ce post).
analysis.F.zip

**paradize3** · 27/11/2007, 01h28

Hello,

Malheureusement je ne connais pas Fortran. As-tu essayer d'executer cela avec un debugger? Ainsi tu trouveras surement la ligne coupable de ton programme.

Je dirais qu'il y a de fortes chances que ca vienne d'un depassement de capacite dans un tableau quelque part.

Salutations,

Gregoire

Erreur Segmentation Violation

MATLAB

Vue hybride

Discussions similaires

Partager

Partager