Skip to content

libundumpi thread value #2

Description

@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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions