Why do I receive a signal SEGV when I'm trying to debug my MEX-file in dbx?

When I try to debug my MEX-file using the command:

matlab -Ddbx

I receive the following output:

 Reading MATLAB

 Reading ld.so.1

 Reading libut.so

 Reading libmx.so

 <SNIP>

When I subsequently enter the command:

run

I receive the following output:

 Running: MATLAB

 (process id 21034)

 Reading atlas_SunUSX.so

 Reading lapack.so

 Reading libsunperf_isa.so.4

 Reading libjava.so

 Reading libjvm.so

 <SNIP>

and error:

 t@17 (l@17) signal SEGV (no mapping at the fault address) in (unknown) at 0x748ac520

 0x748ac520:             bad opcode

 (/opt/SUNWspro/bin/../WS6U2/bin/sparcv9/dbx)

Answer 1

[MathWorks Support Team]

We have verified that there is a problem that affects the way the Sun Java Virtual Machine communicates among threads on Solaris 8. To work around this issue, instead of starting MATLAB with the command:

run

from within dbx, use the command:

run -nojvm