Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Solaris sigbus error in ompi_info
From: Ralph Castain (rhc_at_[hidden])
Date: 2014-01-01 10:56:27

I'm going to split this apart so we can deal with these in a more manageable fashion.

I have no ideas here as there isn't enough info - can you dig deeper to tell us where the sigbus happens?

Meantime, I filed a ticket against it and we can capture your response there.

On Jan 1, 2014, at 1:48 AM, Siegmar Gross <Siegmar.Gross_at_[hidden]> wrote:

> Unfortunately I still get a "SIGBUS Error" on "Solaris Sparc"
> for "ompi_info -a".
> tyr openmpi-1.9 99 ompi_info | grep MPI:
> Open MPI: 1.9a1r30100
> tyr openmpi-1.9 100 ompi_info -a |& grep Signal
> [tyr:09699] Signal: Bus Error (10)
> [tyr:09699] Signal code: Invalid address alignment (1)
> .../openmpi-1.9_64_cc/lib64/
> [ Signal 2099900312 (?)]
> Bus error
> tyr openmpi-1.9 101
> I can compile and run a small MPI program without "SIGBUS Error".
> Jeff, thank you very much for solving this problem.
> tyr small_prog 110 mpicc init_finalize.c
> tyr small_prog 111 mpiexec -np 1 a.out
> Hello!
> tyr small_prog 112