Why not using __FUNCTION__ in all our error messages ???
diff -r 686ec286164a ompi/communicator/communicator.h
--- a/ompi/communicator/communicator.h Tue Sep 08 14:39:03 2009 +0200
+++ b/ompi/communicator/communicator.h Tue Sep 08 15:48:06 2009 +0200
@@ -313,7 +313,7 @@
{
#if OPAL_ENABLE_DEBUG
if(peer_id >= comm->c_remote_group->grp_proc_count) {
- opal_output(0, "ompi_comm_lookup_peer: invalid peer index (%d)", peer_id);
+ opal_output(0, "%s: invalid peer index (%d)", __FUNCTION__,peer_id);
return (struct ompi_proc_t *) NULL;
}
#endif
On Tue, Sep 8, 2009 at 4:49 PM, Arthur Huillet <[email protected]>wrote:
> Hi,
>
> please find attached a patch to ompi/communicator/communicator.h that fixes
> the error message displayed by ompi_comm_peer_lookup() so the function name
> that appears is correct.
>
> --
> Greetings, A. Huillet
>
>
> _______________________________________________
> devel mailing list
> [email protected]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
