byebug 9.0.5 → 11.1.3

data/CONTRIBUTING.md

@@ -26,32 +26,25 @@ abide by its terms.
 
 ## Running the test suite
 
-* Make sure you compile the C-extension using `bundle exec rake compile`.
+* Make sure you compile the C-extension using `bin/rake compile`.
   Otherwise you won't be able to use `byebug`.
-* Run the test suite using the default rake task (`bundle exec rake`). This
-  task is composed of 2 subtasks: `bundle exec rake compile` &&
-  `bundle exec rake test`.
+* Run the test suite using the default rake task (`bin/rake`). This task is
+  composed of 3 subtasks: `bin/rake compile`, `bin/rake test` & `bin/rake lint`.
 * If you want to run specific tests, use the provided test runner, like so:
-  * Specific test files. For example,
-    `script/minitest_runner.rb test/commands/break_test.rb`
-  * Specific test classes. For example,
-    `script/minitest_runner.rb Byebug::BreakAtLinesTestCase`
+  * Specific test files. For example, `bin/minitest test/commands/break_test.rb`
+  * Specific test classes. For example, `bin/minitest BreakAtLinesTest`
   * Specific tests. For example,
-    `script/minitest_runner.rb test_catch_removes_specific_catchpoint`
+    `bin/minitest test_catch_removes_specific_catchpoint`
   * Specific fully qualified tests. For example,
-    `script/minitest_runner.rb
-    BreakAtLinesTest#test_setting_breakpoint_sets_correct_fields`
+    `bin/minitest BreakAtLinesTest#test_setting_breakpoint_sets_correct_fields`
   * You can combine any of them and you will get the union of all filters. For
-    example: `script/minitest_runner.rb Byebug::BreakAtLinesTestCase
+    example: `bin/minitest BreakAtLinesTest
     test_catch_removes_specific_catchpoint`
 
 ## Code style
 
-* Byebug uses [overcommit][] to enforce code style. Install the git hooks using
-  `bundle exec overcommit --install`. They will review your changes before they
-  are committed, checking they are consistent with the project's code style.
-
-[overcommit]: https://github.com/brigade/overcommit/
+* Byebug uses several style checks to check code style consistent. You can run
+  those using `bin/rake lint`.
 
 ## Byebug as a C-extension
 
@@ -60,6 +53,6 @@ functionality is implemented in C (the interaction with the TracePoint API).
 The rest of the gem is implemented in Ruby. Normally you won't need to touch
 the C-extension, but it will obviously depended on the bug you're trying to fix
 or the feature you are willing to add. You can learn more about C-extensions
-[here](http://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1.html)
+[here](https://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1.html)
 or
-[here](http://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2.html).
+[here](https://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2.html).

data/GUIDE.md

@@ -69,12 +69,12 @@ Now let us step through the program.
     5:   tri = 0
     6:
     7:   0.upto(n) { |i| tri += i }
-    9:   end
-   10:
-   11:   tri
-   12: end
-   13:
-=> 14: triangle(3)
+    8:
+    9:   tri
+   10: end
+   11:
+=> 12: t = triangle(3)
+   13: puts t
 (byebug) <RET> # hit enter
 
 [1, 10] in /path/to/triangle.rb
@@ -186,7 +186,21 @@ end
 
 n_args = $ARGV.length
 
-fail('*** Need number of disks or no parameter') if n_args > 1
+raise("*** Need number of disks or no parameter") if n_args > 1
+
+n = 3
+
+if n_args > 0
+  begin
+    n = $ARGV[0].to_i
+  rescue ValueError
+    raise("*** Expecting an integer, got: #{$ARGV[0]}")
+  end
+end
+
+raise("*** Number of disks should be between 1 and 100") if n < 1 || n > 100
+
+hanoi(n, :a, :b, :c)
 ```
 
 Recall in the first section it was stated that before the `def` is run, the
@@ -316,7 +330,7 @@ Now let's see what happens after stepping:
    11:
 => 12: n_args = $ARGV.length
    13:
-   14: fail('*** Need number of disks or no parameter') if n_args > 1
+   14: raise("*** Need number of disks or no parameter") if n_args > 1
 (byebug) private_methods.member?(:hanoi)
 true
 (byebug)
@@ -335,7 +349,7 @@ can use the `restart` command here.
 ```bash
 (byebug) restart 3
 Re exec'ing:
-  /path/to/bin/byebug /path/to/hanoi.rb 3
+  /path/to/exe/byebug /path/to/hanoi.rb 3
 
 [1, 10] in /path/to/hanoi.rb
     1: #
@@ -442,15 +456,15 @@ NameError Exception: undefined local variable or method `n_args' for main:Object
    19:   begin
    20:     n = $ARGV[0].to_i
    21:   rescue ValueError
-   22:     raise("** Expecting an integer, got: #{$ARGV[0]}")
+   22:     raise("*** Expecting an integer, got: #{$ARGV[0]}")
    23:   end
    24: end
    25:
-   26: fail('*** Number of disks should be between 1 and 100') if n < 1 || n > 100
+   26: raise("*** Number of disks should be between 1 and 100") if n < 1 || n > 100
    27:
 => 28: hanoi(n, :a, :b, :c)
 (byebug) n_args
-0
+1
 (byebug) eval n
 3
 (byebug) down 2
@@ -513,8 +527,8 @@ framework for that. Here's the test code, it should be placed in the same
 directory as `triangle.rb`.
 
 ```ruby
-require 'minitest/autorun'
-require_relative 'triangle.rb'
+require "minitest/autorun"
+require_relative "triangle.rb"
 
 class TestTriangle < Minitest::Test
   def test_basic
@@ -522,7 +536,7 @@ class TestTriangle < Minitest::Test
 
     0.upto(5) { |i| solutions << triangle(i) }
 
-    assert_equal([0, 1, 3, 6, 10, 15], solutions, 'First 5 triangle numbers')
+    assert_equal([0, 1, 3, 6, 10, 15], solutions, "First 5 triangle numbers")
   end
 end
 ```
@@ -547,7 +561,7 @@ Run options: --seed 31679
 # Running:
 
 [2, 11] in test_triangle.rb
-    2: require_relative 'triangle.rb'
+    2: require_relative "triangle.rb"
     3:
     4: class TestTriangle < Minitest::Test
     5:   def test_basic
@@ -556,7 +570,7 @@ Run options: --seed 31679
     8:
     9:     0.upto(5) { |i| solutions << triangle(i) }
    10:
-   11:     assert_equal([0, 1, 3, 6, 10, 15], solutions, 'First 5 triangle numbers')
+   11:     assert_equal([0, 1, 3, 6, 10, 15], solutions, "First 5 triangle numbers")
 (byebug)
 ```
 
@@ -599,7 +613,7 @@ We get the same result as if we had run byebug from the outset.
 ### Debugging Oddities: How debugging Ruby may be different from other languages
 
 If you are used to debugging in other languages like C, C++, Perl, Java or even
-Bash (see [bashdb](http://bashdb.sf.net)), there may be a number of things that
+Bash (see [bashdb](http://bashdb.sourceforge.net)), there may be a number of things that
 seem or feel a little bit different and may confuse you. A number of these
 things aren't oddities of the debugger per se but differences in how Ruby works
 compared to those other languages. Because Ruby works a little differently from
@@ -726,7 +740,7 @@ _current_ class of the object.
 Consider the following little Ruby program.
 
 ```ruby
-'Yes it does' =~ /
+"Yes it does" =~ /
 (Yes) \s+
 it  \s+
 does
@@ -939,8 +953,7 @@ We have started by debugging the `employee` thread. To do that, we switch to
 that thread using the `thread switch 3` command. The thread number is the one
 specified by `thread list`, we know this is our worker thread because `thread
 list` specifies where the thread is defined in the file (and its current
-position if the thread is currently running, although this is only available
-since Ruby 2.2.1).
+position if the thread is currently running).
 
 After that we stopped the main thread and the worker thread, using the command
 `thread stop`. We do this because we want to focus on the employee thread first
@@ -1285,7 +1298,7 @@ Running a program from byebug adds a bit of overhead and slows it down a little.
 Furthermore, by necessity, debuggers change the operation of the program they
 are debugging. And this can lead to unexpected and unwanted differences. It has
 happened so often that the term
-[Heisenbugs](http://en.wikipedia.org/wiki/Heisenbug) was coined to describe the
+[Heisenbugs](https://en.wikipedia.org/wiki/Heisenbug) was coined to describe the
 situation where using a debugger (among other possibilities) changes the
 behavior of the program so that the bug doesn't manifest itself anymore.
 
@@ -1298,7 +1311,7 @@ at the same speed as if there were no byebug.
 To enter byebug this way, just drop `byebug` in whichever line you want to start
 debugging at. You also have to require byebug somehow. If using bundler, it will
 take care of that for you, otherwise you can use the ruby `-r` flag or add
-`require 'byebug'` in the line previous to the `byebug` call.
+`require "byebug"` in the line previous to the `byebug` call.
 
 If speed is crucial, you may want to start and stop this around certain sections
 of code, using `Byebug.start` and `Byebug.stop`. Alternatively, instead of
@@ -1314,7 +1327,7 @@ problem you want to investigate. And since `byebug` is just a method call it's
 possible to enclose it in a conditional expression, for example
 
 ```ruby
-byebug if 'bar' == foo and 20 == iter_count
+byebug if "bar" == foo and 20 == iter_count
 ```
 
 ### Restarting Byebug
@@ -1341,9 +1354,9 @@ program that you want to debug (In Rails, the
 `config/environments/development.rb` could be a good candidate).
 
 ```ruby
-  require 'byebug/core'
+  require "byebug/core"
   Byebug.wait_connection = true
-  Byebug.start_server('localhost', <port>)
+  Byebug.start_server("localhost", <port>)
 ```
 
 Once this piece gets executed, you can connect to the remote debugger from your
@@ -1455,6 +1468,7 @@ display a short list of named classes of commands
   save       -- Saves current byebug session to a file
   set        -- Modifies byebug settings
   show       -- Shows byebug settings
+  skip       -- Runs until the next breakpoint as long as it is different from the current one
   source     -- Restores a previously saved byebug session
   step       -- Steps into blocks or methods one or more times
   thread     -- Commands to manipulate threads

data/LICENSE

@@ -1,23 +1,23 @@
-Copyright (c) David Rodríguez <deivid.rodriguez@gmail.com>
+Copyright (c) 2018 David Rodríguez <deivid.rodriguez@riseup.net>
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
-   notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
-   notice, this list of conditions and the following disclaimer in the
-   documentation and/or other materials provided with the distribution.
+modification, are permitted provided that the following conditions are met:
 
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.md

@@ -1,30 +1,25 @@
 # Byebug
 
 [![Version][gem]][gem_url]
-[![Quality][gpa]][gpa_url]
-[![Coverage][cov]][cov_url]
-[![Gratipay][tip]][tip_url]
+[![Tidelift][tid]][tid_url]
 [![Gitter][irc]][irc_url]
 
 [gem]: https://img.shields.io/gem/v/byebug.svg
-[gpa]: https://img.shields.io/codeclimate/github/deivid-rodriguez/byebug.svg
-[cov]: https://img.shields.io/codeclimate/coverage/github/deivid-rodriguez/byebug.svg
-[tip]: https://img.shields.io/gittip/byebug.svg
+[tid]: https://tidelift.com/badges/package/rubygems/byebug
 [irc]: https://img.shields.io/badge/IRC%20(gitter)-devs%20%26%20users-brightgreen.svg
 
 [gem_url]: https://rubygems.org/gems/byebug
-[gpa_url]: https://codeclimate.com/github/deivid-rodriguez/byebug
-[cov_url]: https://codeclimate.com/github/deivid-rodriguez/byebug
-[tip_url]: https://gratipay.com/byebug
+[tid_url]: https://tidelift.com/subscription/pkg/rubygems-byebug?utm_source=rubygems-byebug&utm_medium=readme_badge
 [irc_url]: https://gitter.im/deivid-rodriguez/byebug
 
-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.
+Byebug is a simple to use and feature rich debugger for Ruby. It uses the
+TracePoint API for execution control and the Debug Inspector API for call stack
+navigation. Therefore, Byebug doesn't depend on internal core sources. Byebug is also
+fast because it is developed as a C extension and reliable because it is supported
+by a full test suite.
 
-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:
+The debugger permits the ability to understand 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
@@ -34,26 +29,21 @@ and offers many of the traditional debugging features such as:
 * Tracking: Keeping track of the different values of your variables or the
   different lines executed by your program.
 
-## Build Status
-
-Linux [![Tra][tra]][tra_url]
+## For enterprise
 
-Windows [![Vey][vey]][vey_url]
+Byebug for enterprise is available via the Tidelift Subscription. [Learn
+more][Tidelift for enterprise].
 
-[tra]: https://img.shields.io/travis/deivid-rodriguez/byebug.svg?branch=master
-[vey]: https://ci.appveyor.com/api/projects/status/github/deivid-rodriguez/byebug?svg=true
+## Build Status
 
-[tra_url]: https://travis-ci.org/deivid-rodriguez/byebug
-[vey_url]: https://ci.appveyor.com/project/deivid-rodriguez/byebug
+![ubuntu](https://github.com/deivid-rodriguez/byebug/workflows/ubuntu/badge.svg)
+![windows](https://github.com/deivid-rodriguez/byebug/workflows/windows/badge.svg)
 
 ## Requirements
 
-* Required: MRI 2.0.0 or higher. For debugging ruby 1.9.3 or older, use
-  [debugger].
-* Recommended:
-  * MRI 2.1.8 or higher.
-  * MRI 2.2.4 or higher.
-  * MRI 2.3.0 or higher.
+* _Required_: MRI 2.4.0 or higher.
+* _Recommended_: MRI 2.6.4 or higher (MRI 2.6.0 to 2.6.3 contain a regression
+  causing unbalanced call/return events in some cases, breaking the `next` command).
 
 ## Install
 
@@ -61,72 +51,91 @@ Windows [![Vey][vey]][vey_url]
 gem install byebug
 ```
 
-## Usage
+Alternatively, if you use `bundler`:
 
-Simply drop
+```shell
+bundle add byebug --group "development, test"
+```
+
+## Usage
 
-    byebug
+### From within the Ruby code
 
-wherever you want to start debugging and the execution will stop there.
-If you were debugging Rails, for example, you would add `byebug` to your code.
+Simply include `byebug` wherever you want to start debugging and the execution will
+stop there. For example, if you were debugging Rails, you would add `byebug` to
+your code:
 
 ```ruby
 def index
   byebug
   @articles = Article.find_recent
+end
 ```
 
-And then start a Rails server.
+And then start a Rails server:
 
 ```shell
 bin/rails s
 ```
 
-Once the execution gets to your `byebug` command you will get a debugging prompt.
+Once the execution gets to your `byebug` command, you will receive a debugging prompt.
+
+### From the command line
+
+If you want to debug a Ruby script without editing it, you can invoke byebug from the command line.
+
+```shell
+byebug myscript.rb
+```
 
 ## Byebug's commands
 
-    Command     | Aliases      | Subcommands
-    ----------- |:------------ |:-----------
-    `backtrace` | `bt` `where` |
-    `break`     |              |
-    `catch`     |              |
-    `condition` |              |
-    `continue`  |              |
-    `delete`    |              |
-    `debug`     |              |
-    `disable`   |              | `breakpoints` `display`
-    `display`   |              |
-    `down`      |              |
-    `edit`      |              |
-    `enable`    |              | `breakpoints` `display`
-    `finish`    |              |
-    `frame`     |              |
-    `help`      |              |
-    `history`   |              |
-    `info`      |              | `args` `breakpoints` `catch` `display` `file` `line` `program`
-    `irb`       |              |
-    `kill`      |              |
-    `list`      |              |
-    `method`    |              | `instance`
-    `next`      |              |
-    `pry`       |              |
-    `quit`      |              |
-    `restart`   |              |
-    `save`      |              |
-    `set`       |              | `autoirb` `autolist` `autopry` `autosave` `basename` `callstyle` `fullpath` `histfile` `histsize` `linetrace` `listsize` `post_mortem` `savefile` `stack_on_error` `width`
-    `show`      |              | `autoirb` `autolist` `autopry` `autosave` `basename` `callstyle` `fullpath` `histfile` `histsize` `linetrace` `listsize` `post_mortem` `savefile` `stack_on_error` `width`
-    `source`    |              |
-    `step`      |              |
-    `thread`    |              | `current` `list` `resume` `stop` `switch`
-    `tracevar`  |              |
-    `undisplay` |              |
-    `up`        |              |
-    `var`       |              | `all` `constant` `global` `instance` `local`
+Command     | Aliases         | Subcommands
+-------     | -------         | -----------
+`backtrace` | `bt` `w` `where`|
+`break`     | `b`             |
+`catch`     | `cat`           |
+`condition` | `cond`          |
+`continue`  | `c` `cont`      |
+`continue!` | `c!` `cont!`    |
+`debug`     |                 |
+`delete`    | `del`           |
+`disable`   | `dis`           | `breakpoints` `display`
+`display`   | `disp`          |
+`down`      |                 |
+`edit`      | `ed`            |
+`enable`    | `en`            | `breakpoints` `display`
+`finish`    | `fin`           |
+`frame`     | `f`             |
+`help`      | `h`             |
+`history`   | `hist`          |
+`info`      | `i`             | `args` `breakpoints` `catch` `display` `file` `line` `program`
+`interrupt` | `int`           |
+`irb`       |                 |
+`kill`      |                 |
+`list`      | `l`             |
+`method`    | `m`             | `instance`
+`next`      | `n`             |
+`pry`       |                 |
+`quit`      | `q`             |
+`quit!`     | `q!`            |
+`restart`   |                 |
+`save`      | `sa`            |
+`set`       |                 | `autoirb` `autolist` `autopry` `autosave` `basename` `callstyle` `fullpath` `histfile` `histsize` `linetrace` `listsize` `post_mortem` `savefile` `stack_on_error` `width`
+`show`      |                 | `autoirb` `autolist` `autopry` `autosave` `basename` `callstyle` `fullpath` `histfile` `histsize` `linetrace` `listsize` `post_mortem` `savefile` `stack_on_error` `width`
+`skip`      | `sk`            |
+`source`    | `so`            |
+`step`      | `s`             |
+`thread`    | `th`            | `current` `list` `resume` `stop` `switch`
+`tracevar`  | `tr`            |
+`undisplay` | `undisp`        |
+`untracevar`| `untr`          |
+`up`        |                 |
+`var`       | `v`             | `all` `constant` `global` `instance` `local`
 
 ## Semantic Versioning
 
-Byebug tries to follow [semantic versioning](http://semver.org) and tries to
+Byebug attempts to follow [semantic versioning](https://semver.org) and
 bump major version only when backwards incompatible changes are released.
 Backwards compatibility is targeted to [pry-byebug] and any other plugins
 relying on `byebug`.
@@ -145,11 +154,25 @@ started. Proper documentation will be eventually written.
   connected.
 * [minitest-byebug] starts a byebug session on minitest failures.
 * [sublime_debugger] provides a plugin for ruby debugging on Sublime Text.
+* [atom-byebug] provides integration with the Atom editor [EXPERIMENTAL].
 
 ## Contribute
 
 See [Getting Started with Development](CONTRIBUTING.md).
 
+## Funding
+
+Subscribe to [Tidelift][Tidelift support] to ensure byebug stays actively
+maintained, and at the same time get licensing assurances and timely security
+notifications for your open source dependencies.
+
+You can also help `byebug` by leaving a small (or big) tip through [Liberapay].
+
+## Security contact information
+
+Please use the Tidelift security contact to [report a security vulnerability].
+Tidelift will coordinate the fix and disclosure.
+
 ## Credits
 
 Everybody who has ever contributed to this forked and reforked piece of
@@ -168,3 +191,9 @@ software, especially:
 [ruby-debug-passenger]: https://github.com/davejamesmiller/ruby-debug-passenger
 [minitest-byebug]: https://github.com/kaspth/minitest-byebug
 [sublime_debugger]: https://github.com/shuky19/sublime_debugger
+[atom-byebug]: https://github.com/izaera/atom-byebug
+[Liberapay]: https://liberapay.com/byebug/donate
+[Tidelift]: https://tidelift.com/subscription/pkg/rubygems-byebug?utm_source=rubygems-byebug&utm_medium=readme_text
+[Tidelift for enterprise]: https://tidelift.com/subscription/pkg/rubygems-byebug?utm_source=rubygems-byebug&utm_medium=referral&utm_campaign=github&utm_content=enterprise
+[Tidelift support]: https://tidelift.com/subscription/pkg/rubygems-byebug?utm_source=rubygems-byebug&utm_medium=referral&utm_campaign=github&utm_content=support
+[report a security vulnerability]: https://tidelift.com/security

data/exe/byebug

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "byebug/runner"
+
+Byebug::Runner.new.run

data/ext/byebug/breakpoint.c

@@ -239,7 +239,7 @@ brkpt_source(VALUE self)
 }
 
 static void
-mark_breakpoint(breakpoint_t * breakpoint)
+mark_breakpoint(breakpoint_t *breakpoint)
 {
   rb_gc_mark(breakpoint->source);
   rb_gc_mark(breakpoint->expr);
@@ -491,7 +491,7 @@ find_breakpoint_by_method(VALUE breakpoints, VALUE klass, ID mid, VALUE bind,
 }
 
 void
-Init_breakpoint(VALUE mByebug)
+Init_byebug_breakpoint(VALUE mByebug)
 {
   breakpoint_max = 0;