- Really fix starting
post_mortem
mode in bin/byebug - Fix starting line tracing in bin/byebug
- Fix starting
post_mortem
mode in bin/byebug
show commands
moved to a separatehistory
command.- Byebug.start can't recieve options any more. Any program settings you want applied from the start should be set in .byebugrc.
trace
command has been removed. Line tracing functionality should be enabled through thelinetrace
setting whereas the global variable tracing functionality is now provided through thetracevar
command.version
setting has been removed. It was not really a setting because it couldn't be set. Usebyebug --version
to check byebug's version.arg
setting removed. Program restart arguments should be set throughrestart
command from now on.linetrace_plus
setting has been renamed totracing_plus
.
- Bugfixes
- Fix post_mortem mode
- Command history is also saved after regular program termination, not only
after quitting with the
q
command. - Fix failure when calling Byebug.start with Timeout::timeout (see #54), thanks @zmoazeni!
- Changes
show commands
command for listing history of previous byebug commands now behaves like shell'shistory
command.- Changes in
history
commands: see 50e6ad8 - Changes in
finish
semantics and in the C extension API: see 61f9b4d - The
init
option for Byebug.start has been removed. Information to make therestart
command work is always saved now.
- Features
- Allow disabling post_mortem mode
- Bugfix release (#52, #53 and #54)
- Fix circular dependency that was affecting
pry-byebug
, thanks @andreychernih
- Support for
sublime-debugger
- Fix installation error in Mac OSX (#40), thanks @luislavena
- Use
require
instead ofrequire_relative
for loading byebug's extension library (thanks @nobu) - Adds back
debugger
as an alias tobyebug
(thanks @wallace) - Adds -R option to byebug's binary to specify server's hostname:port for remote debugging (thanks @mrkn)
- Fixes
thread list
showing too many threads - Change in tracing global variables. Use
trace variable foo
instead oftrace variable $foo
- Fix setting post mortem mode with
set post_mortem
. Now this is the only post mortem functionality available as specifyingByebug.post_mortem
with a block has been removed in this version.
- Fixes bug preventing users from deleting breakpoints
- Fix broken test suite
- Compatibility with Phusion Passenger Enterprise (thanks @FooBarWidget)
- More minimalist help system
- Fix another compilation issue in 64 bit systems
- Fix compilation issue introduced by 2.2.0 (#26)
- "show" and "set" option
stack_trace_on_error
is now calledstack_on_error
- Small fixes in stack_size calculations
- Warning free byebug
- Add
verbose
setting for TracePoint API event inspection - Fix setting
post_mortem
mode - Allow
edit <filename>
without a line number
- Fix bug when debugging code inside '-e' flag
- Fix bug in remote debugging display
- Fix bug where eval would crash when inspect raised an exception (reported by @iblue)
enable breakpoints
now enables every breakpointdisable breakpoints
now disables every breakpoint
- Various bug fixes
- "Official" definition of a command API
- Thread support
- More user friendly regexps for commands
- Better help for some commands
save
command now saves the list of "displays"- Fixes bug in calculating stacksize
- Bugfix release
- Remote debugging support
- Callstack display: specifically mark c-frames
- Callstack navigation: skip c-frames
- Callstack navigation: autolist after navigation commands
- Windows compatibiliy: compilation and terminal width issues
byebug
placed at the end of a block or method call now works as expected- Don't autolist when ruby '-e' option is used
- Fixes callstyles. From now on, use 'long' for detailed frames in callstack and 'short' for more concise frames
- No more Byebug.start to get correct callstack information! Dropping
byebug
anywhere and inmediately printing the stack just works now. :)
- Fixes crash when using "help command subcommand"
- Byebug now works with Rails Console debugging flag
- Fix post-mortem mode when running byebug from the outset
- Fix --no-quit flag when running byebug from the outset
- Fixes crash when printing some filenames in backtraces
- Allows byebug developers to easily use compilers different from gcc (thanks @GarthSnyder!)
- Byebug now uses the Debug Inspector API: faster and nicer!
- Fixes bug that prevents some random crashes
- Byebug now works with Rails debugging flag
- Fix bug which would make byebug crash when trying to print lines of code containing the character '%'
- Fix bug which prevented basename and linetrace options from working together
- Support colon-delimited include paths in command-line front-end (@ender672)
- Added 'pry' command.
- Ctrl+C during command line editing is handled and works like pry/irb
- Better help system
- Code cleanup
- First version compatible with pry-byebug
- Post-mortem support
- "autoreload" is set by default now
- "list" command: no negative line numbers shown, and line range behaves as expected at the begining/end of file
- In some weird cases, "backtrace" command segfaults when trying to show info on some frame args. Don't know the reason yet, but the exception is handled now and and the command doesn't segfault anymore.
- Try some thread support (not even close to usable)
- "autolist" and "autoeval" are default settings now
- Fixes bug which messed up the call-stack when manipulating backtrace information and when nexting/stepping
- Corrected small bug preventing byebug from loading
- Green test suite
- Initial release