[petsc-dev] segfaults with mpich 3.2 and clang (Apple LLVM 8.0.0, clang 800.0.42.1)

[Matthew Knepley]

On Fri, Feb 10, 2017 at 2:33 PM, Jeff Hammond <jeff.science at gmail.com>
wrote:

> See https://github.com/elemental/Elemental/issues/200.
>

Excellent find Jeff.

  Matt


> Jeff
>
> On Fri, Feb 10, 2017 at 12:05 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>>
>>   I am using MPICH 3.2 with 8.2.1 and typically run the entire PETSc test
>> suite. Have not observed problems. Maybe upgrade Xcode first?
>>
>>
>> > On Feb 10, 2017, at 1:59 PM, Brad Aagaard <baagaard at usgs.gov> wrote:
>> >
>> > Are there any known issues with mpich3.2 and clang (Apple LLVM 8.0.0,
>> clang 800.0.42.1)? I am getting segfaults in MPI routines within PETSc.
>> > The error is: write_line error; fd=-1 buf=:cmd=abort exitcode=59, which
>> appears to be similar to the recent DMPlexCreateExodusFromFile() does not
>> work on macOS Sierra thread
>> > https://lists.mcs.anl.gov/mailman/htdig/petsc-users/2017-
>> January/031463.html
>> >
>> > However, I am not using any Darwin packaging system like homebrew. I am
>> building PETSc via the PyLith installer which builds mpich, NetCDF, HDF5,
>> etc from scratch using the Apple's clang. If I swap mpich3.2 for
>> mpich3.1.3, these segfaults go away, so I am inclined to blame mpich3.2.
>> >
>> > If this is a unknown or undiagnosed issue, I will try a standalone
>> PETSc install to try to reproduce it.
>> >
>> > Thanks,
>> > Brad
>> >
>> >
>>
>>
>
>
> --
> Jeff Hammond
> jeff.science at gmail.com
> http://jeffhammond.github.io/
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170210/4c9a62f8/attachment.html>