Debugger info widget should consider the call type at the callsite in addition to the function type
Open
Nobody has claimed this yet.
enhancement
Impact: Low
UI
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Right now the debugger info widget displays info for the call using the info from the function itself. This is good in many cases, but it is not perfect, since:
- The call can be a function pointer or data variable, which means it does not have the associated function type
- The call type could have been overridden
- For variadic functions, e.g., printf, the type at the call site could be more accurate
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the debugger info widget and the code that obtains call information from the function type. Trace how the callsite type is represented for function pointers, data variables, overridden call types, and variadic calls. Done means the widget uses the callsite type when it provides more accurate information while preserving the existing function-type behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100