Hi Mike,
I think the reason you aren't seeing that data is because Dyninst
aborted while we were asking it to find the loops in your
application.
You should see a by function list of the performance information as
part of the default view generation from the osspcsamp command.
So, we probably have a Dyninst problem (which we don't see very
often). I'm copying the Dyninst team on this one.
Bill, Dyninst team - do you have any ideas?ÂÂ Have you seen this
type of assert in the past?
Thanks,
Jim G
On 01/25/2016 12:28 PM, Mike Burklund
wrote:
Jim,
Ok I used the full path to mpiexec.hydra and was able to
get further. It complained about not having the env
variable DYNINST_API_RT_LIB set. I set this and ran
again and was able to run. I got this message (not sure
if it is bad or not):
ÂÂÂ ossutil:
/opt/openss-2.2/openspeedshop-release-2.2/BUILD/hornberg/dyninst-8.2.1/dyninstAPI/src/binaryEdit.C:918:
int_variable* BinaryEdit::createTrampGuard():
Assertion `rtlib.size()' failed.
I'm just learning openspeedshop now, but when I look at
the results with openss, it say:
ÂÂÂ (There are no objects specified for the basic Detail
report.)
So, I guess I need to look into how to get sampling/timing
results on the function level of my test application.
Thanks again,
Mike
|
|