Vector35 / Vector35/debugger

LLDB fails attaching to a process when using remote debugging

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

Nobody has claimed this yet.

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

Description

Version and Platform (required):

Client:

  • Binary Ninja Version: 5.1.8104-stable
  • OS: Windows
  • OS Version: 11
  • CPU Architecture: x86-64
  • Local or Remote Debugging: remote debugging

Remote:

  • LLDB Version: 19.1.7
  • OS: Rocky Linux
  • OS Version: 8.10
  • CPU Architecture: x86-64

Bug Description:
When doing remote debugging and trying to attach to process on a remote I get the next error

LLDB Failed to attach to target with "invalid host:port specification:
'[192.168.8.10]'"

Image

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open Binary Ninja's project
  2. On the remote machine run the program and the lldb-server
lldb-server g --attach (pidof crackme-01) 0.0.0.0:31337
  1. In Binary Ninja go to Debugger > Connect to debug server... Followed the steps here
  2. Once connected try attaching to the process by clicking Debugger > Attach to process...
  3. See error

Expected Behavior:
This should work and the debugger should attach to the process

Additional Information:

Doing "remote process" does work

 lldb-server g --attach <PID> 0.0.0.0:31337

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 using the documented remote-debugging connection flow, the Windows 11 client, Rocky Linux 8.10 remote, and LLDB 19.1.7. Compare attaching through “Attach to process...” with the reported working remote-process command and inspect how the host:port value is formed. Done means attaching to the remote process succeeds without the invalid host:port error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, operating-systems, reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.