Vector35 / Vector35/debugger

Debugger related metadata causes merge conflict when merging database

Open
#450 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Impact: Medium
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

The debugger saves some metadata into the database and it may cause merge conflict when merging databases. These include:

  1. debugger.executable_path, as well as other things shown in the debug adapter settings dialog
  2. The Debugger binary view itself. Which will be mitigated by #448
  3. Current program counter. (I am not entirely sure, this is only saved as a line highlight in the debugger binary view, not in the metadata.)

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 by examining how debugger metadata—debug adapter settings, the binary view, and the current program counter—is saved into and merged in the database, while checking #448 for the binary-view mitigation. Done means debugger-related metadata no longer causes merge conflicts, with the intended handling of the current program counter clarified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.