PINCE is a front-end/reverse engineering tool for the GNU Project Debugger (GDB), focused on games.



PINCE is a front-end/reverse engineering tool for the GNU Project Debugger (GDB), focused on games. However, it can be used for any reverse-engineering related stuff. PINCE is an abbreviation for "PINCE is not Cheat Engine". PINCE is in development right now, read Features part of the project to see what is done and Roadmap part to see what is currently planned. Also, please read Wiki Page of the project to understand how PINCE works.

Feel free to join our discord server!

Disclaimer: Do not trust to any source other than Trusted Sources that claims to have the source code or package for PINCE and remember to report them immediately

Disclaimer: YOU are responsible for your actions. PINCE does NOT take any responsibility for the damage caused by the users

Pre-release screenshots:


  • Memory searching: PINCE uses libscanmem to search the memory efficiently [Done]
  • Variable Inspection&Modification [Done/Basic]
    • CheatEngine-like value type support: Byte to 8 Bytes, Float, Double, Strings(including utf-8, utf-16, utf-32 and zero-terminate strings), Array of Bytes [Done]
    • Symbol Recognition: See here [Done]
    • Automatic Variable Allocation: See here [Done]
    • Dynamic Address Table: Supports drag&drop, recursive copy&pasting&inserting and many more [Done]
    • Manual Address Table Update: [Done]
    • Smart casting: PINCE lets you modify multiple different-type values together as long as the input is parsable. All parsing/memory errors are directed to the terminal [Done]
    • Continuous Address Table Update: You can adjust update timer or cancel updating by modifying settings. Non-stop version is Postponed\Quarterway Done [Done\Only works when the inferior is stopped]
    • Variable Locking: PINCE lets you freeze(constantly write a value to memory cell) variables [Done]
  • Memory View [Done/Basic]
    • Infinite Scrolling: PINCE automatically disassembles the next available instruction(s) on mouse wheel/scrollbar move. Instruction count can be changed from settings. Hex View also supports this feature [Done]
    • Dissect Code: You can dissect desired memory regions to find referenced calls, jumps and strings. Disassemble screen will automatically handle the referenced data and show you if there's a referenced address in the current dissasemble view. It can be used from Tools->Dissect Code in the MemoryView window. Using its hotkey instead in the MemoryView window automatically dissects the currently viewed region. You can separately view referenced calls and strings after the search from View->Referenced Calls/Strings. Note: If you decide to uncheck 'Discard invalid strings' before the search, PINCE will try to search for regular pointers as well [Done]
    • Bookmarking: Bookmark menu is dynamically created when right clicked in the disassemble screen. So unlike Cheat Engine, PINCE lets you set unlimited number of bookmarks. List of bookmarks can also be viewed from View->Bookmarks in the MemoryView window. Commenting on an address automatically bookmarks it. [Done]
    • Modify on the fly: PINCE lets you modify registers on the fly. Unlike CE, you can also change XMM and FPU registers. Check GDB expressions in the Wiki page for additional information [Done]
    • Opcode Search: You can search opcodes with python regular expressions. To use this feature, click Tools->Search Opcode in the MemoryView window. [Done]
  • Debugging [Done/Basic]
    • Has basic debugging features such as stepping, stepping over, execute till return, break, continue. Also has breakpoints, watchpoints and breakpoint conditions. Has advanced debugging utilities such as Watchpoint/Breakpoint Tracking and Tracing
    • Chained Breakpoints: Just like CE, PINCE allows you to set multiple, connected breakpoints at once. If an event(such as condition modification or deletion) happens in one of the breakpoints, other connected breakpoints will get affected as well [Done]
    • Watchpoint Tracking: Allows you to see which instructions have been accessing to the specified address, just like "What accesses/writes to this address" feature in CE [Done]
    • Breakpoint Tracking: Allows you to track down addresses calculated by the given register expressions at the specified instruction, just like "Find out what addresses this instruction accesses" feature in CE with a little addon, you can enter multiple register expressions, this allows you to check the value of "esi" even if the instruction is something irrelevant like "mov [eax],edx" [Done]
    • Tracing: Almost the same with CE. But unlike CE, you can stop tracing whenever you want. Created from scratch with shittons of custom features instead of using gdb's trace&collect commands because some people have too much time on their hands [Done]
    • Collision Detection: GDB normally permits setting unlimited watchpoints next to each other. But this behaviour leads to unexpected outcomes such as causing GDB or the inferior become completely inoperable. GDB also doesn't care about the number(max 4) or the size(x86->max 4, x64->max 8) of hardware breakpoints. Fortunately, PINCE checks for these problems whenever you set a new breakpoint and detects them before they happen and then inhibits them in a smart way. Lets say you want to set a breakpoint in the size of 32 bytes. But the maximum size for a breakpoint is 8! So, PINCE creates 4 different breakpoints with the size of 8 bytes and then chains them for future actions [Done]
  • Code Injection [Working on it]
    • Run-time injection: Only .so injection is supported for now. In Memory View window, click Tools->Inject .so file to select the .so file. An example for creating .so file can be found in "libPINCE/Injection/". PINCE will be able to inject single line instructions or code caves in near future [Partially Done?]
  • GDB Console [Done]
    • Is the power of PINCE not enough for you? Then you can use the gdb console provided by PINCE, it's on the top right in main window
  • Simplified/Optimized gdb command alternatives [Working on it]
    • Custom scripts instead of using gdb's x command for reading memory [Done]
    • Custom scripts instead of using gdb's set command for modifying memory [Done]
  • libPINCE- A reusable python library
    • PINCE provides a reusable python library. You can either read the code or check Reference Widget by clicking Help->libPINCE in Memory Viewer window to see docstrings. Contents of this widget is automatically generated by looking at the docstrings of the source files. PINCE has a unique parsing technique that allows parsing variables. Check the function get_comments_of_variables in SysUtils for the details. This feature might be replaced with Sphinx in the future
  • Extendable with .so files at runtime
  • Automatic Trainer Generation: [Planned]
    • PINCE provides a trainer auto-generated from current address table on demand by using libPINCE and PyQT5 together


Clone this repo by running git clone --recursive then run sudo sh in the PINCE directory. Install script currently supports Ubuntu and Debian. For Archlinux, use the AUR package instead.

If you like to uninstall PINCE, just delete this folder. Almost everything is installed locally, including gdb. Config and user files of PINCE can be found in "~/.config/PINCE", you can manually delete them if you want.


  • GDB enhancements (peda, pwndbg, etc) that use a global gdbinit file might cause PINCE to misfunction at times. Please disable them or use them locally before starting PINCE
  • Having spaces in your path might cause GDB to fail compiling

Running PINCE

Just run sh in the PINCE directory

For developers:

sudo apt-get install qttools5-dev-tools (qt5 form designer)
sudo apt-get install pyqt5-dev-tools (pyuic5)
sudo pip3 install line_profiler (for performance testing)

How to use line_profiler: Add @profile tag to the desired function and run PINCE with sudo kernprof -l -v


  • A few weeks till 17/01/2016 : Learned GDB, process of analysis
  • 17/01/2016-22/01/2016 : Basic design, grasping of Python3 and Pyqt5, proof-testing
  • 22/01/2016 : First commit
  • 19/02/2016 : Moved to Github from Bitbucket
  • 25/02/2016 : First successful implementation of thread injection[Update-08/05/2016 : PINCE now uses linux-inject as a secondary injection method]
  • 18/06/2016 : PINCE now supports all-stop mode instead of non-stop mode
  • 21/06/2016 : Variable Inspection&Modification is finished(At basic level)
  • 21/08/2016 : Memory View is finished(At basic level)
  • 24/08/2016 : PINCE no more uses linux-inject because of stability issues(a fix for the race conditions in the inferior would be nice)
  • 26/12/2016 : Debugging is finished(At basic level)
  • 19/05/2020 : libscanmem integration is complete, enjoy memory searching. Huge thanks to fisu, xk and 12345ieee (libscanmem team)

Current Roadmap

  • Refactor file naming conventions(libPINCE->libpince, decide on snake_case or camelCase for modules etc)
  • Create and combine all non-tutorial notes within it
  • Consider replacing read/write_memory_multiple functions with mem_handle&read/write_memory functions, this fixes the "read_memory_multiple follows a bad design pattern" step
  • Implement non-stop Continuous Address Table Update feature
  • Refactorize memory write/read functions
    • ReferencedStringsWidgetForm refreshes the cache everytime the comboBox_ValueType changes, this creates serious performance issues if total results are more than 800k. Only update the visible rows to prevent this(check disassemble_check_viewport for an example)
    • Implement same system for the TrackBreakpointWidgetForm if necessary. Do performance tests
    • Consider using a class instead of primitive return types to store the raw bytes. This also gets rid of the unnecessary parameter only_bytes. This class should also include a method to display None type as red '??' text for Qt
    • text_to_valuetype is a bad design pattern. Store the information inside the items of tableWidget_AddressTable instead
    • read_memory_multiple follows a bad design pattern, use named tuples or something like that
    • Provide an option to cut BOM bytes when writing to memory with the types UTF-16 and UTF-32
    • Put a warning for users about replacement bytes for non UTF-8 types
    • Extend string types with LE and BE variants of UTF-16 and UTF-32
    • Change comboBox_ValueType string order to be ... String_UTF-8 String_Others Array of Bytes
    • Implement a custom combobox class for comboBox_ValueType and create a context menu for String_Others item
  • Indent docstrings properly like GDB_Engine.get_breakpoint_info does(independent from other steps)
  • Implement "Investigate Registers" button to gather information about the addresses registers point to(independent from other steps)
  • Implement selectionChanged signal of lineEdit_HexView
  • Implement multi selection for HexView
  • Add the ability to track down registers and addresses in tracer(unsure)(independent from other steps)
  • Implement CE's Ultimap-like feature for tracing data, dissect code data and raw instruction list. Search for calls and store their hit counts to filter out the functions that haven't or have executed specific number of times. Implement a flexible input field for the execution count. For instance, 2^x only searches for hit counts 2, 4, 8 and so on, 3x only searches for 3, 6, 9 etc.(independent from other steps)(CE#358)
  • Extend search_referenced_strings with relative search
  • Consider adding type guessing for the StackView(independent from other steps)
  • Move GUI classes of to their own files
  • Handle signals and internal errors that causes gdb to halt, such as SIGSEGV and overlapping breakpoints(independent from other steps)
  • Use gdb python API breakpoints instead of breakpoint commands for optimization, also find a way to eliminate output coming from stepping commands such as stepi or nexti(independent from other steps)
  • Implement a psuedo-terminal for the inferior like edb does(independent from other steps)
  • Implement libPINCE engine
  • Implement auto-ESP&aimbot (depends on libPINCE engine)
  • Try to optimize TrackBreakpoint and TrackWatchpoint return data structures further, adding an id field might simplify traversing of the tree, performance tests are required(independent from other steps)
  • Extend tagging system to PINCE GUI functions
  • Implement inject_with_advanced_injection(independent from other steps)
  • Implement single-line code injection
  • Implement multi-line code injection
  • Break on/Catch signals and syscalls
  • Move non-communication functions in GDB_Engine to ScriptUtils and create corresponding fields in GDB_Engine and GDBCommandExtensions automatically. This lets entire functionality of libPINCE to be used with both python scripts and gdb python scripts, thus allowing it to be used as a plugin for projects such as radare2
  • Flowcharts based on disassembled output
  • Automatic function bypassing(make it return the desired value, hook specific parts etc.)
  • Implement speedhack(independent from other steps)
  • Implement unrandomizer(independent from other steps)
  • Implement pointer-scan
  • Write at least one test for each function in libPINCE
  • Migrate to Sphinx documentation from the custom libPINCE documentation(independent from other steps)
  • Embedded tutorial videos
  • Super-Uber-Rad credits roll with chiptune tunes
  • Implement extra MemoryViewerWindow tabs(independent from other steps)
  • Consider removing the command file layer of IPC system for GDB_Engine.send_command to speed up things(independent from other steps)[Update-29/04/2018 : Delaying this until GDB/MI implements a native multiline command feature or improves interpreter-exec command to cover every single multiline command type(including define commands)]
  • Implement thread info widget
  • Add ability to change logo and other assets if people contribute more than one asset per usage. Also consider using PINCE-media for development if needed(independent from other steps)
  • Implement developer mode in settings. Developer mode will include features like dissection of GUI elements on events such as mouse-over(independent from other steps)
  • Add ability to include non-absolute calls for dissect code feature(i.e call rax). Should be considered after the first version release. Might be useful for multi-breakpoint related features
  • Implement toggling of arrows for easier navigation for dissected regions(independent from other steps)
  • Provide information about absolute addresses in disassemble screen(independent from other steps)
  • Use type hints(py 3.5) and variable annotations(py 3.6) when support drops for older systems(independent from other steps)
  • All tables that hold large amount of data should only update the visible rows(check disassemble_check_viewport for an example)(independent from other steps)
  • Add different kinds of themes and the ability to change between them on runtime. Implement dark theme first. Also add the ability to create a custom theme and modify the existing ones(independent from other steps)


GPLv3+. See COPYING file for details

Contact Information

Korcan Karaokçu(korcankaraokcu) [email protected]
Çağrı Ulaş(cagriulas) [email protected]
Jakob Kreuze(TsarFox) [email protected]
Gibus [email protected]

Supported platforms

  • Kubuntu 18.04 & 16.04(Also tested on x86 variants)
  • Debian 9 (Stretch)
  • Kali Linux
  • Parrot OS
  • Linux Mint 19 (Tara)(install the package "python3-psutil" if you encounter ImportError or NameError, thanks Gibus)
  • Archlinux(tag cagriulas or TsarFox when creating an issue)

Trusted Sources

  • Duplication of effort

    Duplication of effort

    I see @korcankaraokcu around the scanmem/GC issues, I thought about paying a courtesy visit.

    On my system I probably need to recompile gdb, as PINCE opens but cannot attach to any process, so I don't have a definite opinion.

    My question is, how much overlap do you have with GC? I know you want to use libscanmem, I'm interested in the gui.

    opened by 12345ieee 23
  • Won't install

    Won't install

    Because the installation insists on gdb 8.2 while my system reports it already has the latest version and refuses to install which causes the whole script to bail outright, please just set your install script to require min gdb 8.2 instead of insisting on that exact version

    opened by awsdert 18
  • Make the address table items store the original address expression

    Make the address table items store the original address expression

    Fixes #45.


    • Since the address table items store address_expr, address_expr needs to be passed into change_address_table_entries.
    • So, calling convention (parameters) of change_address_table_entries is changed, and all of its occurences needs to be modified accordingly. That is a big change and I hope there is no bug.
    • There are some redundant text_to_valuetype and valuetype_to_text calls. To solve it, it's necessary to refactor the code to store the details inside the items ("text_to_valuetype is a bad design pattern. Store the information inside the items of tableWidget_AddressTable instead" inside roadmap)
    opened by user202729 14
  • EOFError when trying to attach

    EOFError when trying to attach

    When trying to attach to a process, command line says

    Last command: pince-get-stack-trace-info
    &"source /tmp/PINCE-connection/10995/gdb_command.txt\n"
    &"Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x850fb148: \n"
    &"/tmp/PINCE-connection/10995/gdb_command.txt:1: Error in sourced command file:\n"
    &"Error occurred in Python command: Cannot access memory at address 0x850fb148\n"
    ^error,msg="/tmp/PINCE-connection/10995/gdb_command.txt:1: Error in sourced command file:\nError occurred in Python command: Cannot access memory at address 0x850fb148"
    Traceback (most recent call last):
      File "", line 1590, in on_process_stop
      File "", line 1680, in update_stacktrace
        stack_trace_info = GDB_Engine.get_stacktrace_info()
      File "/home/trent/PINCE-master/libPINCE/", line 927, in get_stacktrace_info
        contents_recv = send_command("pince-get-stack-trace-info", recv_with_file=True)
      File "/home/trent/PINCE-master/libPINCE/", line 121, in send_command
        output = pickle.load(open(recv_file, "rb"))
    EOFError: Ran out of input

    Then when I try to scan for a value It says

    Exception test
    Traceback (most recent call last):
      File "", line 450, in newfirstscan_onclick
        x = 0 / 0
    ZeroDivisionError: division by zero
    opened by tbillington 14
  • Suggested default icon until you make a logo

    Suggested default icon until you make a logo

    I found one in my pre-installed icons (on manjaro) called custom-toolbox, I think that would be a suitable icon for time being, as for future logo I think a joypad with a wrench on top would make for a good logo since this is focused on cheating, if you want a more general suggestion then the only thing that comes to mind is similar but with a gear instead of a joypad

    opened by awsdert 13
  • Error during process attaching

    Error during process attaching

    OS: Debian 8 x64 Desktop environment: KDE 4

    Traceback (most recent call last):
      File "", line 571, in pushbutton_open_onclick
        code_injection_status = GDB_Engine.attach(str(pid), initial_code_injection_method)
      File "/usr/share/PINCE/", line 213, in attach
      File "/usr/share/PINCE/", line 242, in create_PINCE_IPC_PATH
        is_path_valid(get_PINCE_IPC_directory(pid), "create")
      File "/usr/share/PINCE/", line 208, in is_path_valid
      File "/usr/share/PINCE/", line 221, in fix_path_permissions
        uid = int(os.environ.get('SUDO_UID'))
    TypeError: int() argument must be a string or a number, not 'NoneType'
    opened by davidebeatrici 13
  • Pauses after resuming

    Pauses after resuming

    When I attach a process, the game automatically pauses. (I guess that is fine) However, when I press F3 to resume, it takes about 1 second before it pauses again by itself. If I were to close the memory viewer and press F3 to resume again, it pauses and the memory viewer opens up again.

    I do not believe this is intentionally designed to behave like this (I hope). If there is any additional information I can provide, let me know.

    opened by ivanskodje 12


    sh [sudo] cloversss 的密码:

    ( Gtk-WARNING **: 10:39:10.868: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not() /home/cloversss/PINCE/libpince/libscanmem/ PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded. from gi.repository import Gtk QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000 Detached from the process with PID:-1 Last command: set logging off ^done 0.0013473033905029297 Last command: set logging file /dev/shm/PINCE-connection/-1/gdb_log.txt =cmd-param-changed,param="logging file",value="/dev/shm/PINCE-connection/-1/gdb_log.txt" ^done 0.0006613731384277344 Last command: source /home/cloversss/.config/PINCE/PINCE_USER_FILES/gdbinit ^done 0.000644683837890625 Last command: handle SIGSEGV stop print ^done 0.0009517669677734375 Last command: set logging off ^done 0.0009047985076904297 Last command: set logging file /dev/shm/PINCE-connection/-1/gdb_log.txt ^done 0.0007500648498535156 Traceback (most recent call last): File "/home/cloversss/PINCE/", line 5261, in window = MainForm() File "/home/cloversss/PINCE/", line 375, in init self.memory_view_window = MemoryViewWindowForm(self) File "/home/cloversss/PINCE/", line 2239, in init self.initialize_disassemble_view() File "/home/cloversss/PINCE/", line 2283, in initialize_disassemble_view GuiUtils.center_scroll_bar(self.verticalScrollBar_Disassemble) File "/home/cloversss/PINCE/libpince/", line 77, in center_scroll_bar QScrollBar.setValue((maximum + minimum) / 2) TypeError: setValue(self, int): argument 1 has unexpected type 'float'

    opened by FxmlesXD 11
  • Built gdb segfaults on ubuntu 21.04

    Built gdb segfaults on ubuntu 21.04

    On commit : 90142e02b4e4baf72e4040d478a57494a7a81e4a OS: Ubuntu 21.04, 5.11.0-25-generic #27-Ubuntu SMP

    got this error when I set to absolute path to the built gdb

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2020, resource id: 14683379, major code: 40 (TranslateCoords), minor code: 0
    Detached from the process with PID:-1
    Traceback (most recent call last):
      File "/home/user/PINCE/", line 1790, in accept
      File "/home/user/PINCE/libPINCE/", line 499, in init_gdb
      File "/usr/lib/python3/dist-packages/pexpect/", line 421, in expect_exact
        return exp.expect_loop(timeout)
      File "/usr/lib/python3/dist-packages/pexpect/", line 179, in expect_loop
        return self.eof(e)
      File "/usr/lib/python3/dist-packages/pexpect/", line 122, in eof
        raise exc
    pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.
    <pexpect.pty_spawn.spawn object at 0x7f6be806ba30>
    command: /usr/bin/sudo
    args: [b'/usr/bin/sudo', b'LC_NUMERIC=C', b'/home/user/PINCE/libPINCE/gdb_pince/gdb-8.3.1/bin/gdb', b'--interpreter=mi']

    So I ran gdb inside gdb and its segfaulting, Not sure if i have missed anything gdb --args /home/user/PINCE/libPINCE/gdb_pince/gdb-8.3.1/bin/gdb --interpreter=mi

    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/".
    Program received signal SIGSEGV, Segmentation fault.
      RAX: 0x00007FFFF7F15040  RBX: 0x00007FFFFFFFD940  RCX: 0x0000555555B020DC  RDX: 0x0000000000000000  o d I t s Z a P c 
      RSI: 0x0000000000000000  RDI: 0x00007FFFF7F15198  RBP: 0x00007FFFF6E0B030  RSP: 0x00007FFFFFFFD918  RIP: 0x00007FFFF7B4B959
      R8 : 0x0000555555B020D7  R9 : 0x0000555555E359D0  R10: 0x00000000000001FF  R11: 0x5933A120734F50A4  R12: 0x0000555555DBF250
      R13: 0x00007FFFFFFFD930  R14: 0x0000000000000010  R15: 0x0000000000000000
      CS: 0033  DS: 0000  ES: 0000  FS: 0000  GS: 0000  SS: 002B
    => 0x7ffff7b4b959 <PyEval_ReleaseLock+25>:      mov    rcx,QWORD PTR [rdx+0x10]
       0x7ffff7b4b95d <PyEval_ReleaseLock+29>:      lea    rsi,[rcx+0x40]
       0x7ffff7b4b961 <PyEval_ReleaseLock+33>:      jmp    0x7ffff7b4b760
       0x7ffff7b4b966:      nop    WORD PTR cs:[rax+rax*1+0x0]
       0x7ffff7b4b970 <_PyEval_SignalReceived>:     endbr64 
       0x7ffff7b4b974 <_PyEval_SignalReceived+4>:   mov    rax,QWORD PTR [rdi+0x10]
       0x7ffff7b4b978 <_PyEval_SignalReceived+8>:   push   r12
       0x7ffff7b4b97a <_PyEval_SignalReceived+10>:  push   rbp
    0x00007ffff7b4b959 in PyEval_ReleaseLock () from /lib/x86_64-linux-gnu/
    gdb$ bt
    #0  0x00007ffff7b4b959 in PyEval_ReleaseLock () from /lib/x86_64-linux-gnu/
    #1  0x0000555555885c58 in do_start_initialization () at python/python.c:1740
    #2  _initialize_python () at python/python.c:1828
    #3  0x0000555555983ffe in initialize_all_files () at init.c:204
    #4  0x0000555555935dc9 in gdb_init (argv0=<optimized out>) at top.c:2185
    #5  0x000055555580ad62 in captured_main_1 (context=0x7fffffffda58) at main.c:868
    #6  captured_main (data=0x7fffffffda58) at main.c:1172
    #7  gdb_main (args=0x7fffffffda58, [email protected]=0x7fffffffdb40) at main.c:1198
    #8  0x0000555555626f70 in main (argc=<optimized out>, argv=<optimized out>) at gdb.c:32
    opened by hstejas 10
  • PINCE totally locks down search interface

    PINCE totally locks down search interface

    No matter what I try when I try to hack the memory of game via PINCE it outright refuses to do anything but show the debugger/memory (reader?), I'd like an option to ignore risks and just scan anyway, GameConqueror can get into the same memory just fine but it lacks the ability to search for values based on number of bits which I was trying to use PINCE for but everything is just permanently disabled The game I'm trying is Dragon Quest Builders on RPCS3

    opened by awsdert 10
  • Nested address table

    Nested address table

    Fix #46. I hope there are no bugs left.

    Currently does not support editing multiple addresses at once. Also, GuiUtils.get_current_row only return a row if there is exactly 1 row highlighted.

    Parent reference can be implemented, although it would not be useful until #45 is resolved.

    Will need structured copy/paste later.

    opened by user202729 10
  • Fedora support?

    Fedora support?

    Hey there,

    I'd love to see this packaged for Fedora, as it is a very capable piece of software. Distribution could be made easier using Copr (Fedora's user repository); there's a publishing guide and full user docs that have more information.

    Also, I had to dnf install libtool intltool readline-devel to get to complete correctly on my system, as they are not present by default.

    Thanks, Elliott

    opened by pointydev 0
  • Unable to create io-slave

    Unable to create io-slave

    I get that error popup when I try to open a pct file.

    Clicking ok on the error dialogue closes it and the open file window that is left behind can move to different folders, but is not able to locate any files in any folder, and if I type the file name manually, when I press load I get an error message saying the file could not be found though it definitely exists in the path displayed in the error message.

    I'm running Kubuntu 20.04 which uses

    • KDE Plasma version 5.18.8
    • KDE Framework version 5.68.0
    • Qt version 5.12.8
    • kernel version 5.4.0-109-generic

    The full io-slave error is Unable to create io-slave. Can not create socket for launching io-slave for protocol 'file'.

    opened by Karnor 1
  • New freeze option

    New freeze option

    It would be extremely useful to have the function of freezing the value only when decreasing or increasing.

    For example, we have a variable with a value of 20, if the program tries to decrease the value, it does not change, but when increasing everything works as it should.

    opened by rejedai 3
  • pince-examine-expression causes game to become

    pince-examine-expression causes game to become "not responding"

    I was testing PINCE with Huniepop 2, since it causes Huniepop 1's process to stop, though I might have figured out why... I was testing some vales to see if everything worked when the terminal I started PINCE with started showing these lines image PINCE itself is still working fine, only the game becomes like this: image

    I am running the game using Lutris with the GOG installer and my OS is Manjaro Gnome running on a Surface Pro 5

    opened by WorldTeacher 16
  • Searching for array of bytes does not guarantee searching in read/execute-only segments.

    Searching for array of bytes does not guarantee searching in read/execute-only segments.

    If you find any assembly instruction that you would like to get address of by pattern. If you try searching for it, apparently it won't yield any results, even if you copy bytes directly by inspecting the memory section. On the other hand, when performing similar search for array of bytes for something in data section, pince correctly finds the data.

    opened by eLeCtrOssSnake 4
  • I am trying to make PINCE package on NixOS

    I am trying to make PINCE package on NixOS

    The problems i am facing is that there is not a single image on the buttons and running with sudo fails. The sudo part i will figure out myself. Also it fails to work with GDB and writes that the GDB is not initialized. I may be missing some packages. Please help me make this package reach more users.

    opened by TheK0tYaRa 5
Korcan Karaokçu
Reverse Engineer
Korcan Karaokçu
GDB plugin for streaming defmt messages over RTT from e.g. JLinkGDBServer

Defmt RTT plugin from GDB This small plugin runs defmt-print on the RTT stream produced by JLinkGDBServer, so that you can see the defmt logs in the G

Gaute Hope 1 Dec 30, 2021
The official code of LM-Debugger, an interactive tool for inspection and intervention in transformer-based language models.

LM-Debugger is an open-source interactive tool for inspection and intervention in transformer-based language models. This repository includes the code

Mor Geva 70 May 20, 2022
pdb++, a drop-in replacement for pdb (the Python debugger)

pdb++, a drop-in replacement for pdb What is it? This module is an extension of the pdb module of the standard library. It is meant to be fully compat

null 899 May 20, 2022
Full-screen console debugger for Python

PuDB: a console-based visual debugger for Python Its goal is to provide all the niceties of modern GUI-based debuggers in a more lightweight and keybo

Andreas Klöckner 2.4k May 18, 2022
An improbable web debugger through WebSockets

wdb - Web Debugger Description wdb is a full featured web debugger based on a client-server architecture. The wdb server which is responsible of manag

Kozea 1.5k May 24, 2022
Debugger capable of attaching to and injecting code into python processes.

DISCLAIMER: This is not an official google project, this is just something I wrote while at Google. Pyringe What this is Pyringe is a python debugger

Google 1.6k May 15, 2022
pdb++, a drop-in replacement for pdb (the Python debugger)

pdb++, a drop-in replacement for pdb What is it? This module is an extension of the pdb module of the standard library. It is meant to be fully compat

null 901 May 25, 2022
Graphical Python debugger which lets you easily view the values of all evaluated expressions

birdseye birdseye is a Python debugger which records the values of expressions in a function call and lets you easily view them after the function exi

Alex Hall 1.5k May 22, 2022
Voltron is an extensible debugger UI toolkit written in Python.

Voltron is an extensible debugger UI toolkit written in Python. It aims to improve the user experience of various debuggers (LLDB, GDB, VDB an

snare 5.7k May 18, 2022
NoPdb: Non-interactive Python Debugger

NoPdb: Non-interactive Python Debugger Installation: pip install nopdb Docs: NoPdb is a programmatic (non-interactive) d

Ondřej Cífka 56 May 12, 2022
Tracing instruction in lldb debugger.Just a python-script for lldb.

lldb-trace Tracing instruction in lldb debugger. just a python-script for lldb. How to use it? Break at an address where you want to begin tracing. Im

null 132 May 22, 2022
Full featured multi arch/os debugger built on top of PyQt5 and frida

Full featured multi arch/os debugger built on top of PyQt5 and frida

iGio90 1.1k May 17, 2022
Arghonaut is an interactive interpreter, visualizer, and debugger for Argh! and Aargh!

Arghonaut Arghonaut is an interactive interpreter, visualizer, and debugger for Argh! and Aargh!, which are Befunge-like esoteric programming language

Aaron Friesen 2 Dec 10, 2021
A simple rubber duck debugger

Rubber Duck Debugger I found myself many times asking a question on StackOverflow or to one of my colleagues just for finding the solution simply by d

null 1 Nov 10, 2021
Visual Interaction with Code - A portable visual debugger for python

VIC Visual Interaction with Code A simple tool for debugging and interacting with running python code. This tool is designed to make it easy to inspec

Nathan Blank 1 Nov 16, 2021
Hdbg - Historical Debugger

hdbg - Historical Debugger This is in no way a finished product. Do not use this

Fivreld 2 Jan 2, 2022
Trashdbg - TrashDBG the world's worse debugger

The world's worse debugger Over the course of multiple OALABS Twitch streams we

OALabs 20 Apr 17, 2022
🔥 Pyflame: A Ptracing Profiler For Python. This project is deprecated and not maintained.

Pyflame: A Ptracing Profiler For Python (This project is deprecated and not maintained.) Pyflame is a high performance profiling tool that generates f

Uber Archive 2.9k May 20, 2022
VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution.

VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution.

null 2k May 26, 2022