Question about --force option and CUDA Toolkit SDK
#5
Your change doesn't really make sense to me, because hashcat tries to find and load the library even with the nvrtc64_*_0.dll file name:
https://github.com/hashcat/hashcat/blob/...end.c#L725

maybe your testing/debugging is kind of done wrongly or flawed... you would need to debug that major/minor loop and revert your changes before testing what libraries the inner loop tries to load. Thx




oh, maybe now I got it.... we probably need to do the same loop when using cygwin (not only if windows/cmd was detected)... that could indeed be the case because the library files on the system across cygwin and win will be the same.
therefore, instead of only
Code:
#if   defined (_WIN)

we would need to use:
Code:
#if defined (_WIN) || defined (__CYGWIN__)

and remove the other branch:
Code:
#elif defined (__CYGWIN__)
below the branch/loop.
Could you test this?
Reply


Messages In This Thread
RE: Question about --force option and CUDA Toolkit SDK - by philsmd - 06-29-2020, 09:43 AM