debug
vimspector
Our great sponsors
debug | vimspector | |
---|---|---|
28 | 100 | |
1,081 | 4,011 | |
2.0% | - | |
8.5 | 8.0 | |
10 days ago | 28 days ago | |
Ruby | Vim Script | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
debug
-
Metaprogramming in Ruby: It's All About the Self (2009)
I've written Ruby for coming up on 20 years, so to be honest I haven't paid attention to what is written on that subject in recent years.
Bundler shouldn't be running inside a trap context, but you might be running into a situation where standard input/output from the actual process triggering your breakpoint has been redirected. In that case, ruby-debug[1] is a good option, as you attach to it from outside[2]. Basically, run "rdbg --open yourscript.rb" and then use rdbg -A from another terminal.
You use Pry remotely too[3] if you prefer.
[1] https://github.com/ruby/debug
[2] https://github.com/ruby/debug?tab=readme-ov-file#remote-debu...
[3] https://github.com/Mon-Ouie/pry-remote
-
Ruby 3.3
what is ruby debug not able to do that you want it to do?
https://github.com/ruby/debug
a nice ide integrated experience:
https://code.visualstudio.com/docs/languages/ruby#_debugging...
https://github.com/ruby/vscode-rdbg
https://code.visualstudio.com/docs/editor/debugging
-
Connecting Debugger to Rails Applications
Execution is paused at the breakpoint (which has a little arrow pointing at it). You can then enter commands to the rdbg prompt to control the debugger. For a list of the different commands you can use, visit the documentation for the debug gem.
-
Ask HN: What side projects landed you a job?
In 2017, I wrote a toy language called Goby[1] to learn how Ruby works. A few folks contributed quite a bit to it and one of them later referred me to my previous job (as a backend developer).
Fast-forward to 2021, I got interested in debugging tools so I started contributing to the then newly created Ruby debugger[2]. In less than a year I opened more than a hundred PRs and became the 2nd biggest contributor of it. And that eventually landed me a job to work on Ruby's development tools, like LSP servers, REPLs, and of course, the debugger :-)
[1] https://github.com/goby-lang/goby
[2] https://github.com/ruby/debug
-
Ruby Tip – Interactive debugging without the need for gems
Fun fact, Ruby as a single-threaded language is how most people experience it, but Ruby has a rich cooperative multitasking called Fibers that hopefully is getting more exposure, in amongst a bevy of competing implementations and other also-ran concurrency primitives (besides the usual contenders like Threads, Process fork, foreman that just runs several processes alongside one another...)
https://github.com/ruby/debug/issues/486#issuecomment-157531...
If you want to use debugging and multi-threaded or multi-fiber Ruby at once, you can! You just have to get a bit creative. I always refer back to this thread on the Ruby `debug` gem (though the advice applies to any other REPL you can use) about applying a Mutex. You can use the built-in Fiber.blocking to prevent other fibers from running at the same time as yours, or you can use a Mutex to just ensure that you don't hit the debugger multiple times in the same process IO that would mean you've got multiple REPLs all grappling for the StdIO at once.
For a long time Ruby dev who almost never did concurrency unless it was facilitated by the OS, or before being exposed to it directly in other languages like Go, the Ruby "super power" remains intact, it's just a bit more mysterious with the concurrency stuff added. Ruby has amazing diversity in its concurrency tools, which is a nice way of saying "the language authors decided not to pick a king concurrent runtime/winning gem whilst all of the competing implementations were all a bit nascent and un-fully-formed!"
I like the bruno/fiber-scheduler but it looks like it is not the winner. It should be easy to switch to another fibers implementation, I think async is the crown champion now, but I still haven't been motivated to switch - the fiber-scheduler that is named fiber-scheduler has been good enough for me, despite shortcomings!
-
Debugging Silent Create Action Failures in Rails
Debuggers are powerful tools that allow you to step through your code line-by-line, inspecting variables and understanding the flow of execution. Using debuggers is a whole topic unto itself, and getting into the weeds with that would balloon the scope of this post. If you want more information on using them, I recommend reading the README for rdbg. This is the debugging solution for modern Ruby/Rails development. It's in Ruby's stdlib as of v3.1, and Rails 7+ apps include it in the Gemfile by default. I also recommend this section of the Rails guides for exploring how to use the debug gem with Rails applications.
-
Intro to Trace Inspector that displays Ruby trace logs with pretty UI
Trace Inspector, a tool that displays Ruby trace logs with pretty UI while debugging in VS Code, has recently landed in debug.gem. debug.gem is a Ruby standard debugger library and the default debugger in Rails. Since debug.gem supports VS Code, you can debug Ruby programs in vscode-rdbg.
-
Debugging Help
For newer versions of Rails (introduced in v7): Debug Gem
-
Anyone else working through Michael Hartl's Learn Enough RoR Series that might be able to help me with a failing unit test?
While pry is nice Ruby 2.6+ includes the debug gem in the standard library which avoids the need to install another dependency.
-
What's new in Ruby 3.2's IRB?
Have you tried ruby/debug's catch command? You can do catch Exception to achieve the same effect.
vimspector
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.
- Shape Typing in Python
-
Certain Mapping only when another command was called earlier (lua)
I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).
-
Vimspector – the Vim debugger rules all
The actual title is "Vimspector - A multi-language debugging plugin for Vim".
It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...
-
How to configure vim like an IDE
vimspector
-
I like Tabasco.
I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.
-
Rust, RR, Neovim: A perfect debug combination
You could try vimspector. It's main target is vim and not neovim.
https://github.com/puremourning/vimspector/
-
Vim or Emacs for C++ Coding?
I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).
[0] https://github.com/ycm-core/YouCompleteMe
[1] https://github.com/puremourning/vimspector
[2] https://github.com/dense-analysis/ale
-
My office wants everyone to use vim as the only editor. Has this happened to anyone else?
For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.
What are some alternatives?
Byebug - Debugging in Ruby 2
nvim-dap - Debug Adapter Protocol client implementation for Neovim
Pry - A runtime developer console and IRB alternative with powerful introspection capabilities.
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
.dotfiles - My dotfiles
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
vim-dirvish - Directory viewer for Vim :zap:
ipdb - Integration of IPython pdb
dotfiles - Settings for various tools I use.
omnisharp-roslyn - OmniSharp server (HTTP, STDIO) based on Roslyn workspaces