Re: [OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

A gcc-based build is fine. So, I think this is similar to issue #3992 in which we seem to have decided that /usr/bin/cc (clang) is not to be trusted on this platform. -Paul On Wed, Aug 30, 2017 at 4:49 PM, Paul Hargrove wrote:

Re: [OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

Ralph, See my response to Larry. The impossibly large value was a figment of gdb's imagination. This system has worked for Open MPI when it was still at 11.0. I cannot say if the current problem is w/ FreeBSD-11.1 (e.g. its compiler) or with Open MPI. I am trying a gcc-based build now. -Pau

Re: [OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

Larry, Thanks for the suggestions. The system logs show only Aug 30 14:16:06 freebsd-amd64 kernel: pid 95624 (orterun), uid 19214: exited on signal 11 (core dumped) However, while "nactivequeues" is a 4-byte integer it *does* appear to be misaligned (suggesting to me that "base" is bogus).

Re: [OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

Yeah, that caught my eye too as that is impossibly large. We only have a handful of active queues - looks to me like there is some kind of alignment issue. Paul - has this configuration worked with prior versions of OMPI? Or is this something new? Ralph > On Aug 30, 2017, at 4:17 PM, Larry

Re: [OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

Paul, > (gdb) print base->nactivequeues seems like an extraordinarily large number to me. I don't know what the implications are of the --enable-debug clang option is. Any chance the SEGFAULT is a debugging trap when an uninitialized value is encountered? The other thought I had is an

[OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

I am testing the 2.1.2rc3 tarball on FreeBSD-11.1, configured with --prefix=[...] --enable-debug CC=clang CXX=clang++ --disable-mpi-fortran --with-hwloc=/usr/local The CC/CXX setting are to use the system default compilers (rather than gcc/g++ in /usr/local/bin). The --with-hwloc is to avoid