Debugger Plugins

Open
#737 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ios, objective-c, swift
Domain
devtools, mobile-dev, reverse-engineering

Research direction

Start from the requested plugin behavior and the listed LLDB commands, then determine how the missing device values can be obtained from pymobiledevice3. Done means a plugin can run the requested setup sequence for iOS debugging, or the scope is narrowed to one-click iOS debugging.

Written by the indexing model from the issue text.

Description

enhancement Impact: Medium python api remote debugging

What is the feature you'd like to have?
I'd like to be able to run custom debugger setup commands as part of a plugin.

Is your feature request related to a problem?
I'm making a plugin to make iOS reverse engineering easier (without a jailbroken device). (Overall, I'd like to support more extensive Swift and ObjC analysis using metadata, as well as easy debugging.) I'd like to get one-click connection to debugserver on an iOS device, which would just require running a few custom lldb commands. Specifically, these ones:

(lldb) platform select remote-ios
(lldb) target create {local executable path}
(lldb) script lldb.target.module[0].SetPlatformFileSpec(lldb.SBFileSpec('{bundle path on iOS device}'))
(lldb) process connect connect://{proxy ip}:{port}
(lldb) process launch

where the missing information can be obtained from pymobiledevice3.

Are any alternative solutions acceptable?
One-click support for ios debugging within binja itself would be more than acceptable, but not at all necessary.

Dominant language
C++
Stars
331
Forks
33
No merged PRs in 30d

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.

More from Vector35/debugger

All issues in Vector35/debugger

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.