test3_6 does occasionally leave zombies around; it's testing forced termination of mutatees and it's somewhat brittle.
One workaround is to run the test suite under Jenkins or an equivalent framework that will reap every process in its process tree; that's what we do for our continuous integration (jenkins.dyninst.org). As an added bonus that will take advantage of the test suite's -junit output option, which I suppose I should publicize more... --bw ________________________________________ From: Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of Suman, Preeti <preeti.su...@intel.com> Sent: Thursday, August 3, 2017 5:06 PM To: 'dyninst-api@cs.wisc.edu' Subject: [DynInst_API:] Testsuite-9.3.0 hangs with Intel compiler Hello, I recently built Dyninst-9.3.2 and testsuite-9.3.0 with Intel-17.0.0 compiler on KNL. The testsuite hung after the icpc test_execption result printed and it didn’t complete the runTests: $ ./runTests -icc –icpc …… test_module icpc none 64 disk NA dynamic nonPIC PASSED test_relocations icpc none 64 disk NA dynamic nonPIC PASSED test_type_info icpc none 64 disk NA dynamic nonPIC PASSED test_exception icpc none 64 disk NA dynamic nonPIC PASSED After aborting runTests, the following tests were still running when I did “ps ef”: test3_6.dyn_icpc_64 test3_6.dyn_icc_64 Have you encountered this issue with Intel compilers? Is there a workaround? Thank you, Preeti Suman Software Development Engineer Software and Services Group Intel Corporation, Austin _______________________________________________ Dyninst-api mailing list Dyninst-api@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
