lldbinit | A gdbinit clone for LLDB | Reverse Engineering library

by gdbinit Python Version: v3.0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(8)Vulnerabilities Install Support

kandi X-RAY | lldbinit Summary

lldbinit is a Python library typically used in Utilities, Reverse Engineering applications. lldbinit has no bugs, it has no vulnerabilities and it has low support. However lldbinit build file is not available and it has a Non-SPDX License. You can download it from GitHub.

A gdbinit clone for LLDB aka how to make LLDB a bit more useful and less crappy. (c) Deroko 2014, 2015, 2016 (c) fG! 2017, 2020 - reverser@put.as - No original license by Deroko so I guess this is do whatever you want with this as long you keep original credits and sources references. Original lldbinit code by Deroko @ gdbinit available @ Huge thanks to Deroko for his original effort! Without it this would not exist. Most of gdbinit functions are converted, and a bunch of new functions added. Some of the commands that were passed to lldb command line were converted to internal API.

Support

Quality

Security

License

Reuse

Support

lldbinit has a low active ecosystem.

It has 304 star(s) with 53 fork(s). There are 19 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 5 have been closed. On average issues are closed in 236 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of lldbinit is v3.0

Quality

lldbinit has 0 bugs and 0 code smells.

Security

lldbinit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

lldbinit code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

lldbinit has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

lldbinit releases are not available. You will need to build from source code and install.

lldbinit has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

lldbinit saves you 1488 person hours of effort in developing the same functionality from scratch.

It has 3318 lines of code, 129 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed lldbinit and discovered the below as its top functions. This is intended to give you an instant insight into lldbinit implemented functionality, and help decide if they suit your requirements.

Run findmem command
Evaluate a command
Get the frame from the target
Print color
Handles the debugger stop command
Get the current PC current frame
Disassembler output from start_address
Returns the indirect flow address for src_addr
Show Mach - O load commands
Configures the context of the code window
Set hardware breakpoint
Enable breakpoint
Disable breakpoint
Crack function
Clear breakpoint
Load breakpoints
Print an int3 patched address
Display the Mach - O header
Crack cmd
Insert int3 byte at given address
Execute a stepo instruction
Nop
Run crackcmd_noret
Display memory
Display memory dump
Patch process memory

Get all kandi verified functions for this library.

lldbinit Key Features

No Key Features are available at this moment for lldbinit.

lldbinit Examples and Code Snippets

No Code Snippets are available at this moment for lldbinit.

Community Discussions

Trending Discussions on lldbinit

env: node: No such file or directory

Removed Realm, but still getting this error: module importing failed: invalid token (rlm_lldb.py, line 37) File "temp.py", line 1,

SBData is wrong when SBValue comes from a Swift Dictionary

How to remove Hook 1 (expr -- @import UIKit display @import Appkit) in Xcode console

let lldb's working directory be XCode's project directory

lldb: implement custom command taking user input

lldb process launch fails to resolve ~/path-to-filename

LLDB alias for Swift command

QUESTION

env: node: No such file or directory

Asked 2020-May-28 at 16:26

env: node: No such file or directory

I checked if my directory for node wasn't wrong and it's fine.

I tried these following answers already: 1. https://github.com/nodejs/node-v0.x-archive/issues/3911 2. https://github.com/creationix/nvm/issues/1702 3. browserify error /usr/bin/env: node: No such file or directory

...

ANSWER

Answered 2018-Aug-15 at 09:30

Trynode -v to see whether you've installed node. I think your node not works.
nvm is the environment managment for node. If you are using nvm, you should brew install nvm, and use nvm install version-of-node-you-want-to-install to install node, and use nvm use the-version to let node works.
Whole install chain is:
- brew install nvm, to install nvm, which is environment/version management for node.
- nvm install 10.3.0, to install node and npm
- npm install -g yarn, to install yarn
- use node -v, npm -v, nvm -v, yarn -v to check if they all works.

Source https://stackoverflow.com/questions/50652989

QUESTION

Removed Realm, but still getting this error: module importing failed: invalid token (rlm_lldb.py, line 37) File "temp.py", line 1,

Asked 2019-Nov-30 at 15:45

I tried using Realm with Cocoapods in a project two years ago. Realm didn't work out, so I removed it. Cocoapods didn't work out, so I eventually removed that as well and switched to Carthage.

With the advent of Xcode 11, I started seeing this error:

...

ANSWER

Answered 2019-Nov-30 at 15:45

Uninstalling and reinstalling Xcode did not solve this issue for me.

As per the unaccepted answer in this question,

Remove Realm Model Object from Xcode

I needed to edit ~/.lldbinit. To be honest, I don't completely understand what this file is. It is not easy to get to or to edit.

I found this tutorial from Ray Wenderlich,

https://www.raywenderlich.com/612-custom-lldb-commands-in-practice

found my way to the editor, highlighted the offending line,

Source https://stackoverflow.com/questions/59090655

QUESTION

SBData is wrong when SBValue comes from a Swift Dictionary

Asked 2018-Oct-13 at 00:47

I'm trying to write a Python function to format a Foundation.Decimal, for use as a type summarizer. I posted it in this answer. I'll also include it at the bottom of this answer, with extra debug prints.

I've now discovered a bug, but I don't know if the bug is in my function, or in lldb, or possibly in the Swift compiler.

Here's a transcript that demonstrates the bug. I load my type summarizer in ~/.lldbinit, so the Swift REPL uses it.

...

ANSWER

Answered 2018-Oct-13 at 00:47

This looks like an lldb bug. Please file a bug about this against lldb with http://bugs.swift.org.

For background: there is some magic going on behind your back in the Dictionary case. I can't show this in the REPL, but if you have a [String : Decimal] array as a local variable in some real code and do:

Source https://stackoverflow.com/questions/52767270

QUESTION

How to remove Hook 1 (expr -- @import UIKit display @import Appkit) in Xcode console

Asked 2018-Aug-23 at 17:42

My used command echo display @import UIKit >> ~/.lldbinitecho display @import AppKit >> ~/.lldbinit at mac terminal app to load UIKit in order to print frame or bounds to Xcode console, but when used that command later, Xcode console always print :

...

ANSWER

Answered 2018-Aug-23 at 17:42

You can use:

Source https://stackoverflow.com/questions/51962720

QUESTION

let lldb's working directory be XCode's project directory

Asked 2018-Jun-11 at 23:12

When debugging in XCode (8.0), I'd like to have lldb's working directory to be the respective project directory.

What I'd like to achieve is to access project files from processes that I launch in lldb or in .lldbinit, and I'd like to access them without having to type/know the full path.

For example, I'd like to spawn a local web server with php -S localhost:2345 within the project directory, such that - in debugging mode - I can simulate downloading well known files (instead of accessing them through the bundle).

I've also tried to use environment variables, e.g. platform shell -- cd $PROJECT_DIR or similar, yet without success.

Any ideas?

...

ANSWER

Answered 2018-Jun-11 at 23:12

You can use the Python interpreter to change lldb's working directory. For instance:

Source https://stackoverflow.com/questions/50730297

QUESTION

lldb: implement custom command taking user input

Asked 2018-May-16 at 22:50

I am using python to extend lldb by a custom command gm, which calls a C++ - function cli(const char* params) then. So one can pause xcode (thereby launching lldb) and type...

...

ANSWER

Answered 2018-May-16 at 22:50

Internally lldb keeps a stack of "I/O Handlers" and so for instance expr just pushes the "Expr I/O Handler" onto the stack, collects the input till it is done and then pops itself off the stack and runs the command.

There's what looks like a first sketch of an SB class (SBInputReader) to do this in the C++ SB API's but I don't think it's complete and it isn't currently exposed to Python. So I don't think there's enough wired up for you do to this from Python yet.

Source https://stackoverflow.com/questions/50380468

QUESTION

lldb process launch fails to resolve ~/path-to-filename

Asked 2018-Mar-04 at 06:43

In .lldbinit in macOS 10.13.3 I define an alias:

...

ANSWER

Answered 2018-Mar-04 at 06:43

(lldb) help pro lau
     Launch the executable in the debugger.

Source https://stackoverflow.com/questions/49089332

QUESTION

LLDB alias for Swift command

Asked 2017-May-17 at 18:44

When debugging SQLite queries from FMDB in my app, I sometimes use a command to return all the values in the current row of the result set:

...

ANSWER

Answered 2017-May-17 at 18:44

In a Swift project, po is an alias for expression -O -l swift --. Try substituting it for its definition in your own alias.

Source https://stackoverflow.com/questions/44030319

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install lldbinit

just copy it somewhere and use command script import path_to_script when you want to load it.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: