[padb-users] minfo.x errors

Ashley Pittman ashley at pittman.co.uk
Sat Oct 30 12:17:02 BST 2010


On 29 Oct 2010, at 23:03, Brock Palen wrote:

> Recently I found when I try to run padb 3.0  that I get the error:
> 
> Error running /home/software/rhel5/padb/3.0/minfo.x: Bad exit code 256
> 
> And I get lots of errors like:
> WARNING: Field opal_list_next of type opal_list_item_t not found!
> WARNING: Field opal_list_sentinel of type opal_list_t not found!
> WARNING: Field fl_mpool of type ompi_free_list_t not found!
> WARNING: Field fl_allocations of type ompi_free_list_t not found!
> WARNING: Field fl_frag_class of type ompi_free_list_t not found!
> WARNING: Field fl_frag_size of type ompi_free_list_t not found!
> WARNING: Field fl_frag_alignment of type ompi_free_list_t not found!
> WARNING: Field fl_max_to_alloc of type ompi_free_list_t not found!
> WARNING: Field fl_num_per_alloc of type ompi_free_list_t not found!
> WARNING: Field fl_num_allocated of type ompi_free_list_t not found!
> WARNING: Field ht_table of type opal_hash_table_t not found!
> WARNING: Field ht_table_size of type opal_hash_table_t not found!
> WARNING: Field ht_size of type opal_hash_table_t not found!
> WARNING: Field ht_mask of type opal_hash_table_t not found!
> WARNING: Field req_type of type ompi_request_t not found!
> WARNING: Field req_status of type ompi_request_t not found!
> <snip>
> 
> Any idea why this would happen now?

minfo.x is the small C component of padb that loads the MPI-provided debugger DLL and queries processes to get the message queues, this error message is coming from the MPI library in ompi/debuggers/ompi_common_dll.c:61.  It likely represents a build problem with OpenMPI.  Possibly that you are using static libraries and the correct symbols aren't being exported correctly?  If there was no information available or you are simply not using MPI padb is much better at reporting correct error messages, I suspect that the DLL is warning about missing data but then just using the values anyway and segfaulting which is why you are getting the Bad exit code message.

The rest of the padb functionality should be un-affected.

Ashley.

-- 

Ashley Pittman, Bath, UK.

Padb - A parallel job inspection tool for cluster computing
http://padb.pittman.org.uk





More information about the padb-users mailing list