Does this persist with the latest commit on master? I just merged support for EM_CUDA within the last two weeks.
--bw ________________________________________ From: Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of Hui Zhang <hzhan...@cs.umd.edu> Sent: Thursday, February 1, 2018 1:37 PM To: dyninst-api@cs.wisc.edu Subject: [DynInst_API:] cuda not supported by dyninstAPI? Hello, I'm using DyninstAPI to retrieve source line information from a binary that's built with libcuda.so, but it reports this error: <program name unknown>: error while loading shared libraries: libcuda.so.1: cannot open shared object file: No such file or directory --SERIOUS-- #0: The process exited during startup. This is likely due to one of two reasons: A). The application is mis-built and unable to load. Try running the application outside of Dyninst and see if it loads properly. B). libdyninstAPI_RT is mis-built. Try loadin --FATAL-- #68: Dyninst was unable to create the specified process --FATAL-- #68: create process failed bootstrap error in bpatch.createProcess Is it because dyninstAPI doesn't support cuda? Thanks -- Best regards Hui Zhang Ph.D. candidate in Computer Engineering University of Maryland at College Park _______________________________________________ Dyninst-api mailing list Dyninst-api@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
