Their web site might give a clue that they produce a parallel debugger and profiler integrated with an (Eclipse PPT-like?) GUI. The debugger is based on launching instances of gdb (which isn't trivial at scale).
More to the point, can someone tell me why I should use the profiler rather than the free/gratis tools, like TAU? Their salesman couldn't.
While a full parallel debugger is clearly useful in difficult cases, easily the most useful debugging tool is stack traces, perhaps from openmpi's automatic backtrace or LLNL's STAT. I don't know whether Totalview (proprietary alternative to DDT) was ever seriously used when we had it available to a multi-site project.
From what I recall of prices, if you're going to buy the tools for more cores than on the sort of single node we have, you're talking something like my salary. Then, in practice most university users won't measure or debug anyway, and may not accept deadlock as a concept when systems people do.