Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

{RedHat7,MATLAB} problems redux

0 views
Skip to first unread message

Mark Bartelt

unread,
Jan 24, 2001, 9:12:11 AM1/24/01
to
I've been stung by problems involving RedHat 7.0 and MATLAB (both R11 and
R12). I know that the R11 issue has been discussed here previously (with
the solution allegedly being to install the RPMs for ld.so and libc5) but
so far I haven't noticed anything about R12 problems.

The R12 installation went just fine, but when I try to run MATLAB, here's
what happens:

| Opening Log file: /home/mark/java.log.24748
| Aborted (core dumped)

The java.log file contains the following:

| SIGSEGV 11* segmentation violation
|
| Full thread dump:
| Monitor Cache Dump:
| Registered Monitor Dump:
| Name and type hash table lock: <unowned>
| String intern lock: <unowned>
| JNI pinning lock: <unowned>
| JNI global reference lock: <unowned>
| BinClass lock: <unowned>
| Class loading lock: <unowned (mutex held)>
| Java stack lock: <unowned>
| Code rewrite lock: <unowned>
| Heap lock: <unowned>
| Has finalization queue lock: <unowned>
| Finalize me queue lock: <unowned>
| Monitor registry: <unowned (mutex held)>

Any suggestions? This is a standard RedHat 7.0 distribution (with all of
the packages installed) plus all the 7.0 updates from the RedHat website.
(So far, I haven't yet installed the old RPMs to enable R11 to run, since
I'm a bit concerned about the possibility of this causing something else
to break, once I've got two different (and incompatible) versions of libc
installed.)

Mark Bartelt 626 395 2522
Center for Advanced Computing Research ma...@cacr.caltech.edu
California Institute of Technology http://www.cacr.caltech.edu/~mark

"Clothes not busy being worn are busy drying." -- Dylan, on laundry day
[ singing "It's all right, ma (I'm only bleaching)" ]

Greg Wolodkin

unread,
Jan 24, 2001, 10:29:09 AM1/24/01
to
Hi Mark -
This is a well-known bug in the version of glibc (2.1.92) that Redhat
chose to ship with Redhat 7.0. Any program which uses LinuxThreads is
pretty much guaranteed not to work. The topic has come up in this
newsgroup, though not recently.

We mention the Redhat 7 problems in the release notes. There is also
a tech support SWAT available at http://www.mathworks.com/support ..
search for "redhat 7" and it will be the only hit.

http://www.mathworks.com/support/solutions/data/26841.shtml

The fix is to upgrade to glibc 2.1.94 or better. I'd recommend glibc
2.2 at this point.

A short-term work-around is to start using "matlab -nojvm" which makes
MATLAB a single-threaded program.

Hope this helps -
Greg


In article <94mnrr$oag$1...@localhost.localdomain>,

Ricardo Meleschi

unread,
Feb 24, 2001, 2:32:03 PM2/24/01
to
There is another problem with upgrading GCC that isn't listed on your
website, but was presented in this newsgroup sometime earlier.

When you run a "make install" with gcc, it doesn't by default install
any locale files needed for java to work correctly. Make sure you
fully read the INSTALL file, and run the additional install command
that installs the correct locale, which is en_US if I remember
correctly.

Ricardo

* Greg Wolodkin <gr...@fess.mathworks.com>:

0 new messages