Vector35 / Vector35/debugger

Breakpoint added before starting debugging does not work when using lldb to connect to a gdbserver

Open
#611 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Repro steps:

  1. Download https://crackmes.one/crackme/66b5fa2c90c4c2830c821d0a to a Linux machine
  2. Run gdbserver 0.0.0.0:31337 -- ./crackme666adv
  3. Open the file in bina (on macOS)
  4. Put a breakpoint somewhere in main function
  5. Debugger - Connect to remote process
  6. Input the IP address and connect to it
  7. Run the target until it breaks at the entry point
  8. Resume the target and notice it runs on its own rather than breaking at the breakpoint

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

Reproduce the failure by running the listed crackme under gdbserver and connecting from Binary Ninja on macOS. Start with the remote-process connection and breakpoint handling around the main function; done means a breakpoint set before connecting stops execution after the target resumes.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.