[MPICH2-dev] logging/debug options?

[Ashley Pittman]

On Wed, 2005-10-19 at 15:10 -0500, William Gropp wrote:
> At 10:32 AM 10/19/2005, Ashley Pittman wrote:
> 
> >Is there any documentation that covers what the following macros do and
> >more specifically how to enable them, from looking at configure I've
> >tried --enable-timing=log and --enable-logging=rlog which seems to
> >define MPIDI_FUNC_EXIT but none of the rest.  We've tried to use them
> >correctly in our code but it would be nice to be able to enable them if
> >possible and check they are correct.
> 
> This is something that is evolving in the code.  There's the original 
> design, what got implemented, and what we want implemented.  We're also 
> interested in suggestions (no comments yet, the current code isn't what we 
> want).
> 
> In the 1.0.2p1 release, you might find some documentation in 
> doc/logging/logging.pdf .  There is enough here to let you generate an rlog 
> file.  The description of the printrlog routine is, however, inadequate; if 
> you want to use this routine, you'll need to look at the source files for 
> this (sorry about that; this isn't what we intended).  You are probably 
> better off using jumpshot to read the rlog files.

Ok, I'll take a look, thanks.

> In terms of event logging in the near future, see 
> http://www-unix.mcs.anl.gov/mpi/mpich2/developer/design/debugmsg.htm 
> .  This is implemented in the current development version and is not in the 
> 1.0.2p1 release.  It will be in the upcoming release.  When developing 
> MPICH2, we recommend configuing with --enable-g=dbg,log (the "log" turns on 
> the macros described in that web page).

I've added this option to our build scripts.

> To make use of the xxx_FUNC_ENTER and xxx_FUNC_EXIT macros, you can also 
> define your own logging package.

Is there a logging package that comes as part of mpich2?  I don't so
much want to use them yet but rather make sure they are correct for
future use.  I remember a while ago I found a compile option which
enabled them and I found a lot of our code wouldn't compile because the
states we were using weren't defined.

Going along with this we get several of the following in our build logs,
whilst it's fairly easy to add entries to the file I don't actually know
what format it's supposed to take so I can't tell if I'm doing it right
or not.

Creating the enumeration of logging states into src/include/mpiallstates.h
ERROR: MPID_STATE_MPIDI_ELAN_IPROBE not in a describe_states.txt file
ERROR: MPID_STATE_MPIDI_ELAN_PROBE not in a describe_states.txt file
ERROR: MPID_STATE_MPID_ALLREDUCE not in a describe_states.txt file

Ashley,