From: outlandk on
I'm running a MacBook Intel processor with Matlab 7.2.0.283 (R2006a).
I tried to compile some simple code (not mine) and got a segmentation
error. Upon restart, Matlab won't load in the terminal, it just sits
there. Any thoughts? I believe the error came from the 'imread'
function. Heres the crash dump:


------------------------------------------------------------------------
Segmentation violation detected at Wed Mar 14 15:12:12 2007
------------------------------------------------------------------------

Configuration:
MATLAB Version: 7.2.0.283 (R2006a)
MATLAB License: 180036
Operating System: Darwin 8.8.1 Darwin Kernel Version 8.8.1: Mon Sep
25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 Power
Macintosh
Window System: The XFree86 Project, Inc (40400000), display :0.0
Current Visual: 0x22 (class 4, depth 24)
Virtual Machine: Java is not enabled
Default Charset: ISO-8859-1

r0 = bfff6228 r8 = 072a36a0 r16 = 9000b360 r24 = ebebebeb
r1 = 0000002c r9 = 00000004 r17 = ebebebeb r25 = ebebebeb
r2 = 00001b03 r10 = 0000002c r18 = ebebebeb r26 = ebebebeb
r3 = 00000000 r11 = 00000030 r19 = ebebebeb r27 = ebebebeb
r4 = a00069a0 r12 = 00000000 r20 = ebebebeb r28 = ebebebeb
r5 = a0006de8 r13 = 00000003 r21 = ebebebeb r29 = ebebebeb
r6 = 00000002 r14 = 90018020 r22 = ebebebeb r30 = ebebebeb
r7 = 073fa2d4 r15 = 20000000 r23 = ebebebeb r31 = ebebebeb
cr = ebebebeb lr = ebebebeb xer = ebebebeb ctr = ebebebeb
vrsave = ebebebeb
Stack Trace:


Segmentation violation occurred within signal handler.
Unable to complete stack trace (stack was probably corrupted)

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(a)mathworks.com for automated
analysis.
For your convenience, this information has been recorded in:
/Users/norad/matlab_crash_dump.346

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

Thank you for your assistance. Please save your workspace and restart
MATLAB before continuing your work.

From: arf_arf69 on
On Mar 14, 5:10 pm, "outlandk" <outla...(a)gmail.com> wrote:
> I'm running a MacBook Intel processor with Matlab 7.2.0.283 (R2006a).
> I tried to compile some simple code (not mine) and got a segmentation
> error. Upon restart, Matlab won't load in the terminal, it just sits
> there. Any thoughts? I believe the error came from the 'imread'
> function. Heres the crash dump:
>
> ------------------------------------------------------------------------
> Segmentation violation detected at Wed Mar 14 15:12:12 2007
> ------------------------------------------------------------------------
>
> Configuration:
> MATLAB Version: 7.2.0.283 (R2006a)
> MATLAB License: 180036
> Operating System: Darwin 8.8.1 Darwin Kernel Version 8.8.1: Mon Sep
> 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 Power
> Macintosh
> Window System: The XFree86 Project, Inc (40400000), display :0.0
> Current Visual: 0x22 (class 4, depth 24)
> Virtual Machine: Java is not enabled
> Default Charset: ISO-8859-1
>
> r0 = bfff6228 r8 = 072a36a0 r16 = 9000b360 r24 = ebebebeb
> r1 = 0000002c r9 = 00000004 r17 = ebebebeb r25 = ebebebeb
> r2 = 00001b03 r10 = 0000002c r18 = ebebebeb r26 = ebebebeb
> r3 = 00000000 r11 = 00000030 r19 = ebebebeb r27 = ebebebeb
> r4 = a00069a0 r12 = 00000000 r20 = ebebebeb r28 = ebebebeb
> r5 = a0006de8 r13 = 00000003 r21 = ebebebeb r29 = ebebebeb
> r6 = 00000002 r14 = 90018020 r22 = ebebebeb r30 = ebebebeb
> r7 = 073fa2d4 r15 = 20000000 r23 = ebebebeb r31 = ebebebeb
> cr = ebebebeb lr = ebebebeb xer = ebebebeb ctr = ebebebeb
> vrsave = ebebebeb
> Stack Trace:
>
> Segmentation violation occurred within signal handler.
> Unable to complete stack trace (stack was probably corrupted)
>
> 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 s...(a)mathworks.com for automated
> analysis.
> For your convenience, this information has been recorded in:
> /Users/norad/matlab_crash_dump.346
>
> 2. If the problem is reproducible, please submit a bug report via:
> http://www.mathworks.com/support/contact_us/ts/help_request_1.html
>
> Thank you for your assistance. Please save your workspace and restart
> MATLAB before continuing your work.

one thing that would cause any program on any type computer to hang up
after a crash, is if you have the program set up to restart where you
left off

for instance if your program automatically loads your project at start

try renaming the file that originally caused the fault so that Matlab
can't find it
or rename the module that you compiled

also don't post your license number

good luck

js:)

From: riccardo on
outlandk wrote:
>
>
> I'm running a MacBook Intel processor with Matlab 7.2.0.283
> (R2006a).
> I tried to compile some simple code (not mine) and got a
> segmentation
> error. Upon restart, Matlab won't load in the terminal, it just
> sits
> there. Any thoughts? I believe the error came from the 'imread'
> function. Heres the crash dump:
>
>
>
--------------------------------------------------------------------
> ----
> Segmentation violation detected at Wed Mar 14 15:12:12 2007
>
--------------------------------------------------------------------
> ----
>
> Configuration:
> MATLAB Version: 7.2.0.283 (R2006a)
> MATLAB License: 180036
> Operating System: Darwin 8.8.1 Darwin Kernel Version 8.8.1: Mon
> Sep
> 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 Power
> Macintosh
> Window System: The XFree86 Project, Inc (40400000), display
> :0.0
> Current Visual: 0x22 (class 4, depth 24)
> Virtual Machine: Java is not enabled
> Default Charset: ISO-8859-1
>
> r0 = bfff6228 r8 = 072a36a0 r16 = 9000b360 r24 = ebebebeb
> r1 = 0000002c r9 = 00000004 r17 = ebebebeb r25 = ebebebeb
> r2 = 00001b03 r10 = 0000002c r18 = ebebebeb r26 = ebebebeb
> r3 = 00000000 r11 = 00000030 r19 = ebebebeb r27 = ebebebeb
> r4 = a00069a0 r12 = 00000000 r20 = ebebebeb r28 = ebebebeb
> r5 = a0006de8 r13 = 00000003 r21 = ebebebeb r29 = ebebebeb
> r6 = 00000002 r14 = 90018020 r22 = ebebebeb r30 = ebebebeb
> r7 = 073fa2d4 r15 = 20000000 r23 = ebebebeb r31 = ebebebeb
> cr = ebebebeb lr = ebebebeb xer = ebebebeb ctr = ebebebeb
> vrsave = ebebebeb
> Stack Trace:
>
>
> Segmentation violation occurred within signal handler.
> Unable to complete stack trace (stack was probably corrupted)
>
> 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(a)mathworks.com for automated
> analysis.
> For your convenience, this information has been recorded in:
> /Users/norad/matlab_crash_dump.346
>
> 2. If the problem is reproducible, please submit a bug report
> via:
> <http://www.mathworks.com/support/contact_us/ts/help_request_1.html>
>
> Thank you for your assistance. Please save your workspace and
> restart
> MATLAB before continuing your work.
>
>

I'm afraid my experience is limited to MS OSes, but there are a
couple of things that you may consider anyway:
1) try deleting the toolbox cache, occasionally it gets corrupted by
crashes;
2) modify matlabrc.m, after saving the original, by commenting out
and in pieces of code, until you understand were the problem is.
hth
riccardo
From: outlandk on
Hey, how about that. Renaming the directory worked, how nice.
You know its strange, I took the same code to another computer and
tried it there, and it worked absolutely fine. Ran without a glitch.
Thanks for the help.

On Mar 14, 11:06 pm, arf_ar...(a)yahoo.com wrote:
> On Mar 14, 5:10 pm, "outlandk" <outla...(a)gmail.com> wrote:
>
>
>
> > I'm running a MacBook Intel processor with Matlab 7.2.0.283 (R2006a).
> > I tried to compile some simple code (not mine) and got a segmentation
> > error. Upon restart, Matlab won't load in the terminal, it just sits
> > there. Any thoughts? I believe the error came from the 'imread'
> > function. Heres the crash dump:
>
> > ------------------------------------------------------------------------
> > Segmentation violation detected at Wed Mar 14 15:12:12 2007
> > ------------------------------------------------------------------------
>
> > Configuration:
> > MATLAB Version: 7.2.0.283 (R2006a)
> > MATLAB License: 180036
> > Operating System: Darwin 8.8.1 Darwin Kernel Version 8.8.1: Mon Sep
> > 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 Power
> > Macintosh
> > Window System: The XFree86 Project, Inc (40400000), display :0.0
> > Current Visual: 0x22 (class 4, depth 24)
> > Virtual Machine: Java is not enabled
> > Default Charset: ISO-8859-1
>
> > r0 = bfff6228 r8 = 072a36a0 r16 = 9000b360 r24 = ebebebeb
> > r1 = 0000002c r9 = 00000004 r17 = ebebebeb r25 = ebebebeb
> > r2 = 00001b03 r10 = 0000002c r18 = ebebebeb r26 = ebebebeb
> > r3 = 00000000 r11 = 00000030 r19 = ebebebeb r27 = ebebebeb
> > r4 = a00069a0 r12 = 00000000 r20 = ebebebeb r28 = ebebebeb
> > r5 = a0006de8 r13 = 00000003 r21 = ebebebeb r29 = ebebebeb
> > r6 = 00000002 r14 = 90018020 r22 = ebebebeb r30 = ebebebeb
> > r7 = 073fa2d4 r15 = 20000000 r23 = ebebebeb r31 = ebebebeb
> > cr = ebebebeb lr = ebebebeb xer = ebebebeb ctr = ebebebeb
> > vrsave = ebebebeb
> > Stack Trace:
>
> > Segmentation violation occurred within signal handler.
> > Unable to complete stack trace (stack was probably corrupted)
>
> > 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 s...(a)mathworks.com for automated
> > analysis.
> > For your convenience, this information has been recorded in:
> > /Users/norad/matlab_crash_dump.346
>
> > 2. If the problem is reproducible, please submit a bug report via:
> > http://www.mathworks.com/support/contact_us/ts/help_request_1.html
>
> > Thank you for your assistance. Please save your workspace and restart
> > MATLAB before continuing your work.
>
> one thing that would cause any program on any type computer to hang up
> after a crash, is if you have the program set up to restart where you
> left off
>
> for instance if your program automatically loads your project at start
>
> try renaming the file that originally caused the fault so that Matlab
> can't find it
> or rename the module that you compiled
>
> also don't post your license number
>
> good luck
>
> js:)