KhronosGroup / KhronosGroup/OpenCL-ICD-Loader

Test failing after clean and stock successful build with no warning or errors

Open
#136 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
304
Forks
172
Avg merge
11h 30m
Merged PRs (30d)
1

Description

After following the build instructions completely and with stock cmake params, running tests fail both for Debug and Release config for the following reasons with exit code 0xc0000135 (STATUS_DLL_NOT_FOUND):

icd_loader_test.exe - System Error: The code execution cannot proceed because IcdLog.dll was not found. Reinstalling the program may fix this problem.

If I manually move IcdLog.dll from build\test\log\[Debug,Release] to the directory where icd_loader_test.exe is I get this other error with exit code 0xc0000139 (STATUS_ENTRYPOINT_NOT_FOUND):

icd_loader_test.exe - Entry Point Not Found: The procedure entry point clCreateImageWithProperties could not be located in the dynamic link library C:\Users\Andrea\Downloads\OpenCL-ICD-Loader\build\test\loader_test\Debug\icd_loader_test.exe.

Built with:

Screenshoots:
error_release
error_debug

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README build instructions and the stock CMake configuration, then reproduce the failure for both Debug and Release on Windows. Inspect the test executables under build\test\loader_test and the DLL under build\test\log to trace the reported missing-DLL and missing-entry-point errors. Done means both configurations run icd_loader_test.exe successfully without those errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cmake
Domain
build-system, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.