Search Results for "file type"

Do you ever use print() or log() to debug your code? Of course you do. IceCream, or ic for short, makes print debugging a little sweeter. With arguments, ic() inspects itself and prints both its own arguments and the values of those arguments. Just give ic() a variable or expression and you're done. ic() returns its argument(s), so ic() can easily be inserted into pre-existing code. Additionally, ic()'s output can be entirely disabled, and later re-enabled, with ic.disable() and ic.enable()...

...It supports multiple languages (C++, Python, TCL among others) via the Debug Adapter Protocol (DAP) model and provides an in-editor UI for viewing scopes, variables, stack frames, output windows and more. You configure it per-project via a .vimspector.json file (or per file type) specifying the adapter, launch configuration or attach process. Once configured you can run, pause, step into/out/over, set and clear breakpoints and inspect variables directly in Vim splits or floating windows. The UI is heavy compared to typical Vim plugins (multiple panes, layouts) but it fills the gap for users who want an integrated debug workflow without leaving the editor.

Version 1.1.5 - Added: Added the ability to edit the EMV panel - You can change which tags show, and what order they are in - Added: Tag 9F10 (Issuer Application Data) to which also includes CVR (a subtag of 9F10) - Added: Menu link to the homepage (sourceforge) - Fixed: 9F07/AUC had the wrong tag details - Fixed: File>Close now saves notes and config updates before exiting - Fixed: Tag 95/TVR title had a spelling mistake - Fixed: Homepage wasn't populating EMV page names -...

A standalone powerpc disassembler written as a wrapper over GNU libopcode library. It accepts the opcode ( in hex or decimal ) as it's argument and spits the disassembled output. Recently, a reference assembler has been added. It takes the instruction in string form and spits the assembled 32-bit opcode.It's not fully tested and may not work always.