You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a critical issue while attempting to utilize the clCreateDevice function from the libamdocl64 library provided by the AMD Pro Package for OpenCL development. This issue seems to be affecting not only my project but also the 'hashcat' tool, indicating a potential problem with the library itself.
Steps to Reproduce:
Install the AMD Pro Package for OpenCL.
Compile and run a program that calls the clCreateDevice function using the libamdocl64 library.
Observe that a SIGSEGV (Segmentation Fault) occurs.
Expected Behavior:
The clCreateDevice function should successfully create an OpenCL device without causing a segmentation fault.
Additional Information:
When running the hashcat tool under the GDB debugger:
Thread 13 (Thread 0x7fffe01356c0 (LWP 220044) "hashcat"):
#0 __futex_abstimed_wait_common64 (private=, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55555781ec68) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55555781ec68, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=, cancel=cancel@entry=true) at ./nptl/futex-internal.c:87 #2 0x00007ffff7aa31bb in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55555781ec68, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=) at ./nptl/futex-internal.c:139 #3 0x00007ffff7aadf0f in do_futex_wait (sem=sem@entry=0x55555781ec68, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:111 #4 0x00007ffff7aadfa0 in __new_sem_wait_slow64 (sem=0x55555781ec68, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:183 #5 0x00007fffc4ed86a0 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #6 0x00007fffc4ed84e9 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #7 0x00007fffc4ef25ea in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #8 0x00007fffc4ef326d in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #9 0x00007fffc4e09936 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #10 0x00007fffc4ed86ff in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so #11 0x00007ffff7aa63ec in start_thread (arg=) at ./nptl/pthread_create.c:444 #12 0x00007ffff7b26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Output Produced by clinfo -d 1:0|head -15:
Platform Name AMD Accelerated Parallel Processing
Device Name gfx902
Device Vendor Advanced Micro Devices, Inc.
Device Vendor ID 0x1002
Device Version OpenCL 2.0 AMD-APP (3110.6)
Driver Version 3110.6 (PAL,HSAIL)
Device OpenCL C Version OpenCL C 2.0
Device Type GPU
Device Board Name (AMD) Unknown AMD GPU
Device PCI-e ID (AMD) 0x15d8
Device Topology (AMD) PCI-E, 0000:03:00.0
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Linker Available Yes
Operating System: Kali Linux 2023.3
Compiler: -
hashcat version: v6.2.6
The text was updated successfully, but these errors were encountered:
I encountered a critical issue while attempting to utilize the clCreateDevice function from the libamdocl64 library provided by the AMD Pro Package for OpenCL development. This issue seems to be affecting not only my project but also the 'hashcat' tool, indicating a potential problem with the library itself.
Steps to Reproduce:
Install the AMD Pro Package for OpenCL.
Compile and run a program that calls the clCreateDevice function using the libamdocl64 library.
Observe that a SIGSEGV (Segmentation Fault) occurs.
Expected Behavior:
The clCreateDevice function should successfully create an OpenCL device without causing a segmentation fault.
Additional Information:
When running the hashcat tool under the GDB debugger:
Thread 13 (Thread 0x7fffe01356c0 (LWP 220044) "hashcat"):
#0 __futex_abstimed_wait_common64 (private=, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55555781ec68) at ./nptl/futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55555781ec68, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=, cancel=cancel@entry=true) at ./nptl/futex-internal.c:87
#2 0x00007ffff7aa31bb in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55555781ec68, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=) at ./nptl/futex-internal.c:139
#3 0x00007ffff7aadf0f in do_futex_wait (sem=sem@entry=0x55555781ec68, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:111
#4 0x00007ffff7aadfa0 in __new_sem_wait_slow64 (sem=0x55555781ec68, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:183
#5 0x00007fffc4ed86a0 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#6 0x00007fffc4ed84e9 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#7 0x00007fffc4ef25ea in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#8 0x00007fffc4ef326d in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#9 0x00007fffc4e09936 in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#10 0x00007fffc4ed86ff in ?? () from /opt/amdgpu-pro/lib/x86_64-linux-gnu/libamdocl64.so
#11 0x00007ffff7aa63ec in start_thread (arg=) at ./nptl/pthread_create.c:444
#12 0x00007ffff7b26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Output Produced by
clinfo -d 1:0|head -15
:Platform Name AMD Accelerated Parallel Processing
Device Name gfx902
Device Vendor Advanced Micro Devices, Inc.
Device Vendor ID 0x1002
Device Version OpenCL 2.0 AMD-APP (3110.6)
Driver Version 3110.6 (PAL,HSAIL)
Device OpenCL C Version OpenCL C 2.0
Device Type GPU
Device Board Name (AMD) Unknown AMD GPU
Device PCI-e ID (AMD) 0x15d8
Device Topology (AMD) PCI-E, 0000:03:00.0
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Linker Available Yes
Operating System: Kali Linux 2023.3
Compiler: -
hashcat version: v6.2.6
The text was updated successfully, but these errors were encountered: