Re: [OMPI users] OMPI users] which info is needed for SIGSEGV in Java foropenmpi-dev-124-g91e9686on Solaris

2014-10-25 Thread Gilles Gouaillardet
Hi Siegmar, You might need to configure with --enable-debug and add -g -O0 to your CFLAGS and LDFLAGS Then once you attach with gdb, you have to find the thread that is polling : thread 1 bt thread 2 bt and so on until you find the good thread If _dbg is a local variable, you need to select the

Re: [OMPI users] which info is needed for SIGSEGV in Java foropenmpi-dev-124-g91e9686on Solaris

2014-10-25 Thread Siegmar Gross
Hi Gilles, I changed _dbg to a static variable, so that it is visible in the library, but unfortunately still not in the symbol table. tyr java 419 nm /usr/local/openmpi-1.9.0_64_gcc/lib64/libmpi_java.so | grep -i _dbg [271] | 1249644| 4|OBJT |LOCL |0|18 |_dbg.14258 tyr java 420

Re: [OMPI users] which info is needed for SIGSEGV in Java for openmpi-dev-124-g91e9686on Solaris

2014-10-25 Thread Siegmar Gross
Hello Gilles and Oscar, unfortunately I didn't get anything useful. It's probably my fault, because I'm still not very familiar with gdb or any other debugger. I did the following things. 1st window: --- tyr java 174 setenv OMPI_ATTACH 1 tyr java 175 mpijavac InitFinalizeMain.java