Vector35 / Vector35/debugger

Report windbg/LLDB bugs to upstream and track its progress

Open
#326 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

DbgEng Adapter enhancement Impact: Low LLDB Adapter
Dominant language
C++
Stars
331
Forks
33
No merged PRs in 30d

Description

LLDB:

  1. https://github.com/Vector35/debugger/issues/124
  2. https://github.com/Vector35/debugger/issues/308
  3. https://github.com/Vector35/debugger/issues/327
  4. https://github.com/Vector35/debugger/issues/376

windbg:

  1. https://github.com/Vector35/debugger/issues/421

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

Review the five linked debugger issues, starting with their current status and any existing upstream reports. Determine whether the LLDB and windbg bugs have been reported to the relevant upstream projects, then update the issue with the report links and progress for each item.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.