Next | Query returned 14 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2018-02-28 16:43:08 by Takahiro Kambe | Files touched by this commit (3) | Package updated
Log message:
devel/ruby-byebug: update to 10.0.0

10.0.0 - 2018-01-26

Changed

* Breaking on methods now stops on the first effective line of a method, not
  on the line containing the def keyword.

Added

* Show valid breakpoint locations when invalid location given (#393, @ko1).
* Ruby 2.5.0 support (#397, @yui-knk).
* Log host & port when launching byebug's client in remote mode.
* Some love & tests to remote debugging (#82).
* remote_byebug shortcut to start the most common case for remote debugging
  (#141).

Fixed

* Properly ignore ruby fullpath executable when passed to byebug script
  (#419).
* Remote server crash when interrupting client (#141, #274).
* Control server thread being able to interrupt main thread only a single
  time. (#239).
   2017-08-31 17:15:14 by Takahiro Kambe | Files touched by this commit (3)
Log message:
Update ruby-byebug to 9.1.0.

## 9.1.0 - 2016-08-22

### Added

* Better UI messages for breakpoint management.

### Fixed

* `where` command failing on instance_exec block stack frames.
* `restart` command crashing in certain cases because of a missing `require \ 
'English'` (#321, @akaneko3).
* `restart` command crashing when debugged script is not executable or has no \ 
shebang (#321, @akaneko3).

### Removed

* Ruby 2.0 and Ruby 2.1 official & unofficial support. Byebug no longer installs
  on these platforms.
   2017-07-31 00:32:28 by Thomas Klausner | Files touched by this commit (229)
Log message:
Switch github HOMEPAGEs to https.
   2017-07-13 16:36:27 by Takahiro Kambe | Files touched by this commit (5)
Log message:
Add ruby-byebug package version 9.0.6.

Byebug is a simple to use, feature rich debugger for Ruby 2. It uses the new
TracePoint API for execution control and the new Debug Inspector API for call
stack navigation, so it doesn't depend on internal core sources. It's developed
as a C extension, so it's fast. And it has a full test suite so it's reliable.

It allows you to see what is going on _inside_ a Ruby program while it executes
and offers many of the traditional debugging features such as:

* Stepping: Running your program one line at a time.
* Breaking: Pausing the program at some event or specified instruction, to
  examine the current state.
* Evaluating: Basic REPL functionality, although [pry] does a better job at
  that.
* Tracking: Keeping track of the different values of your variables or the
  different lines executed by your program.

Next | Query returned 14 messages, browsing 11 to 20 | previous