KhronosGroup / KhronosGroup/OpenCL-Layers

Param verification layer: prominently documented symbol for hooking in debuggers

Open
#18 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
13
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Especially for the parameter verification layer it would be *immensely* useful to have a well documented function name that gets called whenever the layer reports an issue. That way, people could define a breakpoint in their debugger and simply look at the callstack to see where the problem occurred (and what the offending parameters were).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the parameter verification layer's issue-reporting path. Identify where reported issues can expose a stable, documented function name suitable for debugger breakpoints, and verify that the call stack still shows the offending parameters. Done means the hook is documented and is invoked whenever the layer reports an issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.