nvim-gdb - Neovim thin wrapper for GDB and LLDB

  •        96

Gdb and LLDB integration with NeoVim. It is instantly usable: type dd, edit GDB launching command, hit . Or type dl to do the same with LLDB backend.

https://github.com/sakhnik/nvim-gdb

Tags
Implementation
License
Platform

   




Related Projects

MIEngine - The Visual Studio MI Debug Engine ("MIEngine") provides an open-source Visual Studio Debugger extension that works with MI-enabled debuggers such as gdb, lldb, and clrdbg

  •    CSharp

The Visual Studio MI Debug Engine ("MIEngine") provides an open-source Visual Studio extension that enables debugging with debuggers that support the gdb Machine Interface ("MI") specification such as GDB, LLDB, and CLRDBG.Before you contribute, please read through the contributing and developer guides to get an idea of requirements for pull requests.

RakNet - RakNet is a cross platform, open source, C++ networking engine for game programmers.

  •    C

------------------------------------------ See Help\swigtutorial.html Upgrading from version 3 ------------------------------------------ See 3.x_to_4.x_upgrade.txt Windows users (Visual Studio 2008 and 2010) ----------------------------------------- Load RakNet_VS2008.sln and convert if necessary.After the project conversion, if you encounter error MSB4006,follow the steps below to fix it:1. Open project properties2. Click on "Common Properties"3. Click on "Framework and References"4. Look

kernel - The Redox microkernel

  •    Rust

Running qemu with the -s flag will set up qemu to listen on port 1234 for a gdb client to connect to it. To debug the redox kernel run. This will start a VM with and listen on port 1234 for a gdb or lldb client.

GDB/Machine Interface library

  •    C

A GDB/MI interface library for C and C++. It implements the GDB/MI (GNU DeBugger/Machine Interface) protocol as a library so you can create a GDB frontend without writing the quot;dialogquot; with GDB. Unlinke CLI the MI is intended for programs and not hu

gdbgui - Browser-based frontend to gdb (gnu debugger)

  •    Javascript

A modern, browser-based frontend to gdb (gnu debugger). Add breakpoints, view stack traces, and more in C, C++, Go, and Rust! Simply run gdbgui from the terminal and a new tab will open in your browser. gdbgui is easy to get started with yet supports scripting, and has terminal access while keeping the user interface in lock step with the underlying gdb process.


GDB remote user interface

  •    C

GDB remote user interface(GDBRUI) is a patch of GDB. This patch will add a interpreter that called RUI to GDB. After add this interpreter, GDB can be controlled by the other programe(such as an IDE) through TCP.

gef - GEF - GDB Enhanced Features for exploit devs & reversers

  •    Python

GEF is a kick-ass set of commands for X86, ARM, MIPS, PowerPC and SPARC to make GDB cool again for exploit dev. It is aimed to be used mostly by exploiters and reverse-engineers, to provide additional features to GDB using the Python API to assist during the process of dynamic analysis and exploit development. It has full support for both Python2 and Python3 indifferently (as more and more distros start pushing gdb compiled with Python3 support).

gdb-dashboard - Modular visual interface for GDB in Python

  •    Python

Modular visual interface for GDB in Python. This comes as a standalone single-file .gdbinit which, among the other things, enables a configurable dashboard showing the most relevant information during the program execution. Its main goal is to reduce the number of GDB commands issued to inspect the current program status allowing the programmer to focus on the control flow instead.

ccdebug

  •    C++

ccdebug is a Qt-based graphical gdb debugger frontend. It uses the gdb/mi quot;machine interfacequot;, and consists of the main program and a generic gdb/mi-plugin quot;migdbplugin.soquot; communicating with gdb.

ArxLibertatis - Cross-platform port of Arx Fatalis, a first-person role-playing game

  •    C++

Arx Libertatis is based on the publicly released Arx Fatalis source code. The source code is available under the GPLv3+ license with some additional terms - see the COPYING and LICENSE files for details. While the crash reporter can be run without GDB, it's main usefulness comes from generating and submitting detailed back-traces in the event of a crash. On non-window systems we use GDB, the GNU Debugger, to accomplish that. If you want to help out the arx project, please install GDB before running arx. GDB is however purely a run-time dependency and is not needed when building the crash reporter.

hijack - Provides an irb session to a running ruby process.

  •    Ruby

Hijack allows you to connect to any ruby process and execute code as if it were a normal irb session. Hijack does not require your target process to require any hijacking code, hijack is able to connect to any ruby process. It achieves this by using gdb to inject a payload into the process which starts up a DRb server, hijack then detaches gdb and reconnects via DRb. Please note that gdb will halt your target process while it is attached, though the injection process is very quick and your process should only be halted for a few milliseconds. Hijack uses DRb over a unix socket file, so you need to be on the same machine as the process you want to hijack. This is by design for security reasons. You also need to run the hijack client as the same user as the remote process.

trivial gdb

  •    C

Trivial GDB (tgdb) is a library for making front ends to GDB using a simple API. Included with tgdb is a lightweight, but fully functional curses front end called cgdb.

JTAG-GDB Server for ARM

  •    C

The quot;JTAG-GDB serverquot; is a program for integrating the ARM-Embedded ICE logic with the GNU-Debugger GDB.

GDB Stub for ARMs JTAG interface

  •    

GDB Remote Stub Backend for debugging an embedded ARM system via JTAG common hardware debug interface. Communication is done via standard TCP/IP GDB Remote Serial Protocol.

nvim-completion-manager - :warning: PLEASE USE https://github.com/ncm2/ncm2 INSTEAD

  •    Python

This is a fast, extensible, async completion framework for neovim. For more information about plugin implementation, please read the Why section. Future updates, announcements, screenshots will be posted here. Subscribe it if you are interested.

neovim-remote - :ok_hand: Support for --remote and friends.

  •    Python

If you encounter any issues, e.g. permission denied errors or you can't find the nvr executable, read INSTALLATION.md. Nvim always starts a server. Get its address via :echo $NVIM_LISTEN_ADDRESS or :echo v:servername. Or specify an address at startup: NVIM_LISTEN_ADDRESS=/tmp/nvimsocket nvim.

inspector - A drop-anywhere C++ REPL

  •    C++

Allows to inject a fully-functional C++17 REPL into running, compiled programs that can access your program state and offers features like code-completion and syntax highlighting. Note that for some linux distributions the cling project also provide pre-build binaries.

nvim-typescript - Typescript tooling for Neovim

  •    Javascript

First make sure you have Neovim 0.2.1 or highter. This includes the node-host that is required for this plugin. You will need a global install of the neovim client as well. This will make sure that neovim and node can communicate.

NyaoVim - Web-enhanced Extensible Neovim Frontend

  •    TypeScript

This is a Neovim frontend built on Electron. The Neovim editor is composed as a Web Component and users can extend the UI with reusable Web Components, HTML, CSS and JavaScript. Use Vim as a component from a shell or in an IDE.