On 4/6/2013 11:10 PM, Corinna Vinschen wrote:
On Apr 6 21:44, marco atzeri wrote:
On 4/3/2013 4:22 PM, Corinna Vinschen wrote:
On Apr 3 15:30, marco atzeri wrote:
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
The crash occurs in a forked process, I guess. Since you're building
the stuff
On 4/3/2013 4:22 PM, Corinna Vinschen wrote:
On Apr 3 15:30, marco atzeri wrote:
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
The crash occurs in a forked process, I guess. Since you're building
the stuff yourself, maybe you can try some serious `printf' based
debugging?
very curious,
On Apr 6 21:44, marco atzeri wrote:
On 4/3/2013 4:22 PM, Corinna Vinschen wrote:
On Apr 3 15:30, marco atzeri wrote:
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
The crash occurs in a forked process, I guess. Since you're building
the stuff yourself, maybe you can try some serious
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
Hi Marco,
On Apr 1 17:11, marco atzeri wrote:
I am building and testing openmpi-1.7.0rc9 on
CYGWIN_NT-6.1 1.7.18(0.263/5/3) 2013-03-28 22:07 x86_64 Cygwin
every looks fine except when all the processes on several cores
end and should return to
On Apr 3 15:30, marco atzeri wrote:
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
Hi Marco,
On Apr 1 17:11, marco atzeri wrote:
I am building and testing openmpi-1.7.0rc9 on
CYGWIN_NT-6.1 1.7.18(0.263/5/3) 2013-03-28 22:07 x86_64 Cygwin
every looks fine except when all the processes
Hi Marco,
On Apr 1 17:11, marco atzeri wrote:
I am building and testing openmpi-1.7.0rc9 on
CYGWIN_NT-6.1 1.7.18(0.263/5/3) 2013-03-28 22:07 x86_64 Cygwin
every looks fine except when all the processes on several cores
end and should return to lunching program, something go wrong
(of
I am building and testing openmpi-1.7.0rc9 on
CYGWIN_NT-6.1 1.7.18(0.263/5/3) 2013-03-28 22:07 x86_64 Cygwin
every looks fine except when all the processes on several cores
end and should return to lunching program, something go wrong
(of course on 32bit everyhing is OK)
Attached stackdump.
