Re: reliable seg fault

[Mike Miller]

On Tue, 25 Oct 2011, Przemek Klosowski wrote:

> On 10/25/2011 01:50 AM, Mike Miller wrote:
>
> > Another question:  Isn't there a command that can be run within Octave, 
> > or maybe a command-line option when calling Octave, that tells us 
> > something about how it was compiled?
>
> The shell command line command using backquotes:
>
> ldd `which octave`
>
> tells you which libraries the octave binary is linked against.


Yep, I was also looking at ldd last night and I did figure out a few 
things.  By the way, in bash shell the back ticks are deprecated and we 
are supposed to use $() instead, which is actually really cool because we 
can nest them.

ldd $(which octave)

I have a system with compute nodes and a head node.  When an octave job 
runs on a compute node, it is executing the same octave file as does the 
head node, but the libraries are on the local HDD of the compute node.  So 
I ran this on a compute node...

md5sum $(ldd $(which octave) | awk '{print $3}') > ~/md5s.txt

...and then I returned to the head node and did this:

md5sum --check ~/md5s.txt

It showed me that 19 of 25 dynamically-linked library files were different 
between nodes even though they are executing the same octave binary.

So we will re-install Octave.  I think the problem is that we upgraded the 
head node so that it had a different architecture than previously, and 
different from the compute nodes.


> In Octave you can print the variable
>
> octave_config_info
>
> which specifically shows the BLAS_LIBS configuration.

That's the one I was looking for.  Thanks.

Mike