libundumpi thread value

[dorier]

When reading a trace with libundumpi, the "thread" value passed to callbacks is always 0, regardless of the rank of the process that generated the trace in the first place. This is at least the case for traces available here: http://portal.nersc.gov/project/CAL/designforward.htm
(it can easily be checked by using dumpi2ascii, too).