Yes, that should work fine if you either assemble the necessary dependencies or
open precisely the binaries you need (and if what you want is just to do static
analysis, it's generally better not to create a process).
--bw
From: Hui Zhang
Sent: Thursday,
Oopsmy fault. I need to submit it as a job to run, but I forget to do
that with dyninst.
Btw, I can still parse the addresses if I treat it as a static binary
instead of a process so that I can do it locally, right?
Thanks
On Thu, Feb 1, 2018 at 3:31 PM, Bill Williams wrote:
> This looks to
This looks to me like libcuda.so is not in the library search path when you
launch the executable. Does vecAddSub run without Dyninst from this same
environment?
From: Hui Zhang
Sent: Thursday, February 1, 2018 2:26 PM
To: Bill Williams
Cc: John Mellor-Cr
I can't figure out the problem from the log. Thanks!
On Thu, Feb 1, 2018 at 3:17 PM, Bill Williams wrote:
> Run with DYNINST_DEBUG_STARTUP=1 in your environment and if the problem
> isn't immediately clear to you from the log, send me stderr from that run.
>
> --bw
>
Run with DYNINST_DEBUG_STARTUP=1 in your environment and if the problem isn't
immediately clear to you from the log, send me stderr from that run.
--bw
From: Hui Zhang
Sent: Thursday, February 1, 2018 2:13 PM
To: John Mellor-Crummey
Cc: Bill Williams; dyn
Hello, John
You mean a full path to the executable? Yes, I tried both, it didn't make a
difference.
I can use addr2line to get the source line info (for the frames in cuda
runtime or the user code), and the stack trace I'm parsing is on the host
side. Both the dyninst and the binary seem to be bui
Bill,
The EM_CUDA support should have nothing to do with this. libcuda.so.1 is a host
binary.
Hui,
Did you use a full path to the file?
FYI: libcuda.so.1 is typically stripped.
> On Feb 1, 2018, at 1:55 PM, Bill Williams wrote:
>
> Does this persist with the latest commit on master? I just
Oh, I didn't know that. I'll try that
Thanks!
On Thu, Feb 1, 2018 at 2:55 PM Bill Williams wrote:
> 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 on beh
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 on behalf of Hui Zhang
Sent: Thursday, February 1, 2018 1:37 PM
To: dyninst-api@cs.wisc.edu
Subject: [DynInst_API:]
Hello,
I'm using DyninstAPI to retrieve source line information from a binary
that's built with libcuda.so, but it reports this error:
: 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.
10 matches
Mail list logo
