Solaris 10 (5.10 Generic_144500-19) patch killed Matlab?!

Hi, I recently patched my V240 box and matlab now gives the dreaded segmentation fault when I try to fire it up. I see an old reference to this question from 2009, but the patch referenced there (117461) has been obsoleted by several others. So, my question is, how to discover the culprit patch so that I can back it out? Thanks for any help - I'm new at this...

[GlennC]

we are experiencing similar.

we are running r2009a sol64

we installed solaris u10.

when we run "matlab" or "matlab -nodesktop", we get seg fault.

It runs fine under Solaris 10, U9 patched to CPU 2011-07.

However, when we apply the kernel patch (144500-19), matlab immediately seg faults. So, our situation seems worse than yours.

One thing we have used in the past with display problems is:

matlab -softwareopengl

It isn't helping us in this case.

So, I guess this is mostly a "me too" comment.

[Judy Gaukel]

No, matlab -softwareopengl is not working here, either.

[GlennC]

i was mixing up the nodisplay and nodesktop options. As with you, the -nodisplay option prevents the seg fault. So, our situation is no better and no worse than yours. it stinks the same.

[Judy Gaukel]

Which matlab do you have - 2009a or 2009b? I see 2009b is the last supported.

We're running 2009a - I'm wondering if you have 2009b (or if I should install 2009b and see if that fixes things). Ugh!

[GlennC]

Judy,

we're running 2009a. Until we got this seg-fault and started looking into it, we believed 2009a to be the terminal release for SPARC Solaris. Anyway, my cell mate says he downloaded 2009b Service Pack 1 and tried to start it and got the seg-fault straight away, same as for 2009a. We have launched a Service Request under our Oracle Maintenance. Will let you know if they fix it.

NTW, I did confirm that, prior to 144500-19, MATLAB worked and immediately foolowing the application of 144500-19, matlab seg-faulted. You could try to patchrm the patch, but if you did a lot of them, it's a pain.

glenn

[Judy Gaukel]

Thanks, Glenn! Saved me repeating that fun experience with 2009b. I'll give removing 144500-19 a kick, and see what happens. Of course, it is required by 143643, and then... what a can of worms. Definitely interested in what Oracle says - maybe I should launch a request as well so they pay attention...

Judy

[GlennC]

unfortunately, Oracle took a brief look at the core dump info and says the problem is within the MATLAB code. I need to follow up with Mathworks.

[Judy Gaukel]

Oh no! Well - keep me posted. I emailed the PCA keeper (how I patch) about it as well.

Answer 1

[Andreas Goser]

MathWorks Technical Support can provide a way to work around the issue. Please contact Technical Support and refer to the internal solution 1-FPZPAJ.

[ELIA Y MATSUMOTO]

Hi Andreas, do you know if, in R2012a, applications built on Linux work on Solaris 10 (5.10)? Thanks, Best Regards, Elia Matsumoto

[Andreas Goser]

Elia, what a pleasure to "meet" you again here! No, I do not know that, but MATLAB Answers is the ideal place to ask this, as there are still some users in Finance, Aero and some research institutes using Solaris.

[ELIA Y MATSUMOTO]

Hi Andreas, thank you for the answer. I getting in touch with MathWorks technical suppor team and R2012a applications build on LINUX environment really do no work on Solaris. The suggested workaround is to build an applications server in LINUX and use RMI connection to access the applications from the SUN environment. I have not tried it yet. Best regards, Elia

Answer 2

[Judy Gaukel]

I backed out the patch 144500-19 and matlab works again.

Answer 3

[Philippe]

Hello, I've the same problem. In my case matlab start only with the "-nodisplay" argument otherwise the segmentation fault occurs immediatly.

Help is very welcome ? Thank's

Answer 4

[Judy Gaukel]

Haven't gotten any further. Our system behaves the same - will start with -nodisplay but crashes otherwise. Our version of Matlab is Version 7.8.0.347 (R2009a) 64-bit (sol64).

So it must be a patch that alters display, somehow.... thanks...

Answer 5

[GlennC]

We were experiencing this same issue, as mentioned in the comments.

We updated our release to R2009b SP1 and then applied a patched library which Mathworks provided to us.

The patched library is:

$MATLAB_HOME/bin/sol64/libmwuix.so

I don't know if they made this available via download or not. We got it through our maintenance agreement.

Note that, once this was applied we had terrible performance issues. Also, if we tried to print to a PNG file, matlab would hang. If we tried a second time, our login session would crash. These issues may be related, somewhat, to the fact we are using SunRays.

work around this issue by starting with -softwareopengl option.

we also use the -nodesktop option here.

So, to summarise:

- apply Solaris Update 10

- install R2009b SP1

- apply patched libmwuix.so lib

- run with -softwareopengl