Re: [OMPI users] Crash in _int_malloc via MPI_Init
On 15 June 2008 at 17:11, Brian Barrett wrote: | On Jun 15, 2008, at 2:20 PM, Dirk Eddelbuettel wrote: | | > Yup: I still suspect compiler / linker changes in Ubuntu between Gutsy | > (released Oct 2007) and Hardy (April 2008). | > | > Why? Because the exactly same source package for Open MPI (as | > maintained by | > Manuel and myself for Debian) works for me on Ubuntu Hardy __if I | > compile it | > on Ubuntu Gutsy__. | > | > Now, I reported this to Ubuntu ... for no answer. Lucas and | > Christoph at | > Debian today released a feature allowing us Debian maintainers to | > see which | > our packages have bugreports in Ubuntu. It was only through this | > mechanism | > that I learned that the segfault I saw with Rmpi (using Open MPI) | > had been | > experienced by someone else, and that a similar bug occurs with | > Python use on | > top of Open MPI. | > | > But still no tangible answer from Canonical / Ubuntu other that some | > reshuffling of bug reports titles and numbers. Very disappointing. | > | > I am CCing Steffen and Andreas who've seen similar bugs and are | > awaiting | > answers too. I am also CCing Cesare at Ubuntu who did the bug | > rearrangement, | > maybe he will find a moment to share their plans with us. | | I suppose I'm glad that it doesn't look like an Open MPI problem. Due Yup. Just heard from the fellow at Ubuntu/Canonical: they broke things via LDFLAGS="-Wl,-Bsymbolic" which makes Open MPI fall on its face due to the three distinct libraries... Setting LDFLAGS="" as we do for Debian overcomes the problem. Cheers, Dirk | to continual problems with the ptmalloc2 code in Open MPI, we've | decided that for v1.3, we'll extract that code out into its own | library. Users who need the malloc hooks for InifiniBand support | (only a small number of applications really benefit from it) will have | to explicitly link in the extra library. Hopefully, this will resolve | some of these headaches. -- Three out of two people have difficulties with fractions.
Re: [OMPI users] Crash in _int_malloc via MPI_Init
On Jun 15, 2008, at 2:20 PM, Dirk Eddelbuettel wrote: Yup: I still suspect compiler / linker changes in Ubuntu between Gutsy (released Oct 2007) and Hardy (April 2008). Why? Because the exactly same source package for Open MPI (as maintained by Manuel and myself for Debian) works for me on Ubuntu Hardy __if I compile it on Ubuntu Gutsy__. Now, I reported this to Ubuntu ... for no answer. Lucas and Christoph at Debian today released a feature allowing us Debian maintainers to see which our packages have bugreports in Ubuntu. It was only through this mechanism that I learned that the segfault I saw with Rmpi (using Open MPI) had been experienced by someone else, and that a similar bug occurs with Python use on top of Open MPI. But still no tangible answer from Canonical / Ubuntu other that some reshuffling of bug reports titles and numbers. Very disappointing. I am CCing Steffen and Andreas who've seen similar bugs and are awaiting answers too. I am also CCing Cesare at Ubuntu who did the bug rearrangement, maybe he will find a moment to share their plans with us. I suppose I'm glad that it doesn't look like an Open MPI problem. Due to continual problems with the ptmalloc2 code in Open MPI, we've decided that for v1.3, we'll extract that code out into its own library. Users who need the malloc hooks for InifiniBand support (only a small number of applications really benefit from it) will have to explicitly link in the extra library. Hopefully, this will resolve some of these headaches. Brian -- Brian Barrett Open MPI developer http://www.open-mpi.org/
Re: [OMPI users] Crash in _int_malloc via MPI_Init
On 15 June 2008 at 15:53, Andreas Klöckner wrote: | On Mittwoch 14 Mai 2008, Andreas Klöckner wrote: | > Hi there, | > | > I would like to put this crash bug [1] that Sam Adams pointed out back on | > the radar--I ran into this, and there's also an Ubuntu bug [2] (which also | > contains my stack trace). | > | > Anybody have an idea what could cause this? | > | > Thanks, | > Andreas | > | > [1] http://www.open-mpi.org/community/lists/users/2007/08/3844.php | > [2] https://bugs.launchpad.net/bugs/210273 | | Dirk Eddelbuettel has pinpointed this to (likely) be a binutils issue (in | Ubuntu, among others, not in Debian) | | See https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/234837 Yup: I still suspect compiler / linker changes in Ubuntu between Gutsy (released Oct 2007) and Hardy (April 2008). Why? Because the exactly same source package for Open MPI (as maintained by Manuel and myself for Debian) works for me on Ubuntu Hardy __if I compile it on Ubuntu Gutsy__. Now, I reported this to Ubuntu ... for no answer. Lucas and Christoph at Debian today released a feature allowing us Debian maintainers to see which our packages have bugreports in Ubuntu. It was only through this mechanism that I learned that the segfault I saw with Rmpi (using Open MPI) had been experienced by someone else, and that a similar bug occurs with Python use on top of Open MPI. But still no tangible answer from Canonical / Ubuntu other that some reshuffling of bug reports titles and numbers. Very disappointing. I am CCing Steffen and Andreas who've seen similar bugs and are awaiting answers too. I am also CCing Cesare at Ubuntu who did the bug rearrangement, maybe he will find a moment to share their plans with us. Tschoe, Dirk | Andreas | | ___ | users mailing list | us...@open-mpi.org | http://www.open-mpi.org/mailman/listinfo.cgi/users -- Three out of two people have difficulties with fractions.
Re: [OMPI users] Crash in _int_malloc via MPI_Init
On Mittwoch 14 Mai 2008, Andreas Klöckner wrote: > Hi there, > > I would like to put this crash bug [1] that Sam Adams pointed out back on > the radar--I ran into this, and there's also an Ubuntu bug [2] (which also > contains my stack trace). > > Anybody have an idea what could cause this? > > Thanks, > Andreas > > [1] http://www.open-mpi.org/community/lists/users/2007/08/3844.php > [2] https://bugs.launchpad.net/bugs/210273 Dirk Eddelbuettel has pinpointed this to (likely) be a binutils issue (in Ubuntu, among others, not in Debian) See https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/234837 Andreas
