Our great sponsors
debug | Byebug | |
---|---|---|
28 | 15 | |
1,077 | 3,321 | |
2.0% | - | |
8.5 | 0.0 | |
10 days ago | 5 months ago | |
Ruby | Ruby | |
BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" License |
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.
Byebug
-
Why does pry/Zeitwerk have issues loading constants in breakpoint context?
Just pry or with byebug? If the latter: https://github.com/deivid-rodriguez/byebug/issues/564
-
How can you debug Rspec tests with VSCode?
Byebug is not fully compatible with Zeitwerk, I was getting random NameError exceptions failing to load constants in development and tests until I removed this gem.
-
Improve Code in Your Ruby Application with RubyCritic
byebug - this elevates debugging Ruby applications. It allows you to run a program line by line, add breakpoints, and evaluate and track values at runtime. If you still use puts for debugging, it's time you get to know Byebug's features and commands.
-
From byebug to ruby/debug
Immune from the compatibility issue with Zeitwerk
-
Ruby on Rails(ROR) development environment setup(Mac OS)
For debugging purposes, I recommend a few gems that will get you started and allow you to play with ruby code in your terminal and manage ruby gems. Gems like bundler pry and byebug do it good and you can check out the official docs, Pry, Byebug, Bundler, These gems need to be accessed globally.
-
Bust Bugs with the Byebug Bug Debugger
Byebug is a helpful and easy-to-use debugger made for Ruby. It allows developers to use traditional debugging features to help identify what is happening in a program while it's running. Byebug was created by David Rodriguez in hopes of building a better Ruby debugger.
-
What gem is used with conjunction with "pry" for step by step debugging?
Others have been suggesting byebug, but for us it started causing random constant loading errors on Ruby 3 in Rails, due to Zeitwerk compatibility issues. So I'm quite happy that the debug gem came in as a replacement. I did like that pry-byebug allows stepping in a normal Pry console, I expect the debug gem will require some getting used to.
-
Some Helpful Ruby Gems
As far as debugging tools go, the Byebug and Pry are two of the best gems I have found. They are used in different contexts, but for all intents and purposes, including them in your code will halt an operation and allow you to access whatever point in the code you halted within your terminal with a REPL.
-
Rails 7 introduces a new debugging gem
We commonly use byebug for debugging our code which is an easy-to-use, feature-rich ruby debugger. This gem is introduced in Rails 5. It offers features like Stepping, Breaking, Evaluating and Tracking.
-
Rails 7 replaced byebug with ruby/debug
Looking forward to this, byebug's Zeitwerk incompatibility is currently causing nondeterministic constant loading errors in our app when used with pry-byebug.
What are some alternatives?
Pry - A runtime developer console and IRB alternative with powerful introspection capabilities.
Pry Byebug - Step-by-step debugging and stack navigation in Pry
vimspector - vimspector - A multi-language debugging system for Vim
debase
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
.dotfiles - My dotfiles
ruby_jard - Just Another Ruby Debugger. Provide a rich Terminal UI that visualizes everything your need, navigates your program with pleasure, stops at matter places only, reduces manual and mental efforts. You can now focus on real debugging.
vim-dirvish - Directory viewer for Vim :zap:
Seeing Is Believing - Displays the results of every line of code in your file
dotfiles - Settings for various tools I use.
Leaky Gems - A list of Ruby gems that have known memory leaks (and issues)