Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.2.1rc1r3540
Start time: Mon Jul 4 21:03:32 EDT 2011
End time: Mon Jul 4 21:05:48 EDT 2011
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.3a1r3537
Start time: Mon Jul 4 21:01:02 EDT 2011
End time: Mon Jul 4 21:03:31 EDT 2011
Your friendly daemon,
Cyrador
Hi, here is the result:
ehhexxn@oak:~/git/test$ mpirun -n 2 -mca btl tipc,self valgrind
./hello_c > 11.out
==30850== Memcheck, a memory error detector
==30850== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==30850== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h
Keep in mind, too, that opal_object is the "base" object -- put in C++ terms,
it's the abstract class that all other classes are made of. So it's rare that
we could create a opal_object by itself. opal_objects are usually created as
part of some other, higher-level object.
What's the full
On Jul 3, 2011, at 8:40 PM, Kawashima wrote:
>> Does your llp sed path order MPI matching ordering? Eg if some prior isend
>> is already queued, could the llp send overtake it?
>
> Yes, LLP send may overtake queued isend.
> But we use correct PML send_sequence. So the LLP message is queued as
Ah -- so this is in the template code. I suspect this code might have bit
rotted a bit. :-\
If you run this through valgrind, does anything obvious show up? I ask because
this kind of error is typically a symptom of the real error. I.e., the real
error was some kind of memory corruption
All this should be fixed now, and the configure output is now clear (it
doesn't change its mind about pci_init/cleanup or pci_lookup_name
without any obvious reason anymore).
FC7:
checking for pci/pci.h... yes
checking for pci_init in -lpci... no
checking for pci_init in -lpci with -lz... yes
Yes, it is a opal_object.
And this error seems to be caused by these code:
void mca_btl_template_proc_construct(mca_btl_template_proc_t*
template_proc){
...
.
/* add to list of all proc instance */
OPAL_THREAD_LOCK(_btl_template_component.template_lock);
Le 03/07/2011 23:55, Jiri Hladky a écrit :
> Hi all,
>
> I have come across tests/hwloc_distances test and I believe that it
> would be great to convert this into the utility
> "hwloc-report-instances" published under utils/ directory. Please let
> me know what you think about it.
>
> It would
