debug 1.0.0.beta1 → 1.0.0.beta2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 99f9de5fc37782d330788a745b34666e07d37c9e168eb7b0361d3b51b8247b56
-  data.tar.gz: 3e6941a9b066ec0965e576b87c8e0cc0bc787571fa5331ca962d906611c368e5
+  metadata.gz: e0ed57ff87f1864d86d79c435081b12df6cb35bd4f24a3cb79f4a909887e5f41
+  data.tar.gz: c342d515e9358e0cfdee353b5d5be1fbbb7bcf46cfdf3f925ace7a3acc2b6e90
 SHA512:
-  metadata.gz: a279de53e047d52c18c0b1c726da4bbf6efbd116f2957f3fa1c106fec929bb0dc903274d9fce8bb03a787f7ca31edd09d54a09b572027485c5a985205e518582
-  data.tar.gz: 5c436bdfa54ab8d2ece8c07fdac31481f0a9e4922ac433e871c09dd0b161d812eaf7c417189e0e9582421d8405a5169ec826065930c3a7441fdd72953c2786de
+  metadata.gz: 112d49a60540e034752e1c3d3721c213549cae4653c63041c3f3da08cf7bf01624e8a45c0ee88ff31270eef337cf8db3ca8de7d403eea550aff82621050e9e14
+  data.tar.gz: e6800fb760a734419ed43fa04720b0bc75a815f0de4511df7f76a44b9b864c002eb6c9503f74e1a9471d335f671f0db12636e852cc6bac0366ba00d051e29b0b

data/README.md

@@ -74,7 +74,7 @@ $ ruby target.rb
 ```
 
 When you run the program with the debug console, you will see the debug console prompt `(rdbg)`.
-The debuggee program (`target.rb`) is suspended at the beggining of `target.rb`.
+The debuggee program (`target.rb`) is suspended at the beginning of `target.rb`.
 
 You can type any debugger's command described bellow. "c" or "continue" resume the debuggee program.
 You can suspend the debuggee program and show the debug console with `Ctrl-C`.
@@ -137,7 +137,7 @@ $ rdbg  ~/src/rb/target.rb
  b => 2
  c => 3
 
-(rdbg) c                                                # Contineu the program ("c" is a short name of "continue")
+(rdbg) c                                                # Continue the program ("c" is a short name of "continue")
 [6]
 ```
 
@@ -173,12 +173,12 @@ Debugger can attach via UNIX domain socket (/home/ko1/.ruby-debug-sock/ruby-debu
 ```
 
 It runs target.rb and accept debugger connection within UNIX domain socket.
-The debuggee process waits for debugger connection at the beggining of `target.rb` like that:
+The debuggee process waits for debugger connection at the beginning of `target.rb` like that:
 
 ```
 $ rdbg -O ~/src/rb/target.rb
 DEBUGGER: Debugger can attach via UNIX domain socket (/home/ko1/.ruby-debug-sock/ruby-debug-ko1-29828)
-DEBUGGER: wait for debuger connection...
+DEBUGGER: wait for debugger connection...
 ```
 
 You can attach the program with the following command:
@@ -204,7 +204,7 @@ and you can input any debug commands. `c` (or `continue`) continues the debuggee
 You can detach the debugger from the debugger process with `quit` command.
 You can re-connect to the debuggee process by `rdbg -A` command again, and the debuggee process suspends the execution (and debugger can input any debug commands).
 
-If you don't want to stop the debuggee process at the beggining of debuggee process (`target.rb`), you can use the fowllowings to specify "non-stop" option.
+If you don't want to stop the debuggee process at the beginning of debuggee process (`target.rb`), you can use the following to specify "non-stop" option.
 
 * Use `rdbg -n` option
 * Set the environment variable `RUBY_DEBUG_NONSTOP=1`
@@ -282,7 +282,7 @@ $ rdbg --attach hostname 12345
 
 If there are `.rdbgrc` files are there at the current directory and the home directory, files are loaded as initial scripts which contains debugger commands. `RUBY_DEBUG_INIT_SCRIPT` environment variable can specify the initial script file.
 
-Initial scripts are evaluted at the first suspend timing (generally, it is the beggining of the target script). For example, you can set break points with `break file:123`.
+Initial scripts are evaluated at the first suspend timing (generally, it is the beginning of the target script). For example, you can set break points with `break file:123`.
 
 If there are `.rdbgrc.rb` files at the current directory and the home directory, files are loaded as a ruby script at the initializing timing.
 
@@ -290,7 +290,7 @@ If there are `.rdbgrc.rb` files at the current directory and the home directory,
 
 You can control debuggee's behavior with environment variables:
 
-* `RUBY_DEBUG_NONSTOP`: 1 for nonstop at the beggining of program.
+* `RUBY_DEBUG_NONSTOP`: 1 for nonstop at the beginning of program.
 * `RUBY_DEBUG_INIT_SCRIPT`: Initial script path loaded at the first stop.
 * `RUBY_DEBUG_COMMANDS`: Debug commands invoked at the first stop. Commands should be separated by ';;'.
 * `RUBY_DEBUG_SHOW_SRC_LINES`: Show n lines source code on breakpoint (default: 10 lines).
@@ -308,7 +308,7 @@ You can control debuggee's behavior with environment variables:
 * [debug command compare sheet - Google Sheets](https://docs.google.com/spreadsheets/d/1TlmmUDsvwK4sSIyoMv-io52BUUz__R5wpu-ComXlsw0/edit?usp=sharing)
 
 You can use the following debug commands. Each command should be written in 1 line.
-The `[...]` notation means this part can be elimiante. For example, `s[tep]` means `s` or `step` are valid command. `ste` is not valid.
+The `[...]` notation means this part can be eliminate. For example, `s[tep]` means `s` or `step` are valid command. `ste` is not valid.
 The `<...>` notation means the argument.
 
 ### Control flow
@@ -366,7 +366,7 @@ The `<...>` notation means the argument.
   * Show current frame's source code from the line <start> to <end> if given.
 * `edit`
   * Open the current file on the editor (use `EDITOR` environment variable).
-  * Note that editted file will not be reloaded.
+  * Note that edited file will not be reloaded.
 * `edit <file>`
   * Open <file> on the editor.
 * `i[nfo]`
@@ -390,7 +390,7 @@ The `<...>` notation means the argument.
 * `f[rame]`
   * Show current frame.
 * `f[rame] <framenum>`
-  * Specify frame. Evaluation are run on this frame environement.
+  * Specify frame. Evaluation are run on this frame environment.
 * `up`
   * Specify upper frame.
 * `down`
@@ -428,9 +428,9 @@ The `<...>` notation means the argument.
 exe/rdbg [options] -- [debuggee options]
 
 Debug console mode:
-    -n, --nonstop                    Do not stop at the beggining of the script.
-    -e [COMMAND]                     execute debug command at the beggining of the script.
-    -O, --open                       Start debuggee with opning the debagger port.
+    -n, --nonstop                    Do not stop at the beginning of the script.
+    -e [COMMAND]                     execute debug command at the beginning of the script.
+    -O, --open                       Start debuggee with opening the debugger port.
                                      If TCP/IP options are not given,
                                      a UNIX domain socket will be used.
         --port=[PORT]                Listening TCP/IP port
@@ -454,11 +454,10 @@ Attach mode:
                       debugger connection, list possible debuggee names.
   'exe/rdbg -A path' tries to connect via UNIX domain socket with given path name.
   'exe/rdbg -A port' tries to connect localhost:port via TCP/IP.
-  'exe/rdbg -A host port' tris to connect host:port via TCP/IP.
+  'exe/rdbg -A host port' tries to connect host:port via TCP/IP.
 
 ```
 
 # Contributing
 
 Bug reports and pull requests are welcome on GitHub at https://github.com/ruby/debug.
-

data/ext/debug/extconf.rb

@@ -1,2 +1,2 @@
 require 'mkmf'
-create_makefile 'debug'
+create_makefile 'debug/debug'

data/lib/debug/breakpoint.rb

@@ -123,7 +123,7 @@ module DEBUGGER__
     def activate_exact iseq, events, line
       case
       when events.include?(:RUBY_EVENT_CALL)
-        # "def foo" line set bp on the beggining of method foo
+        # "def foo" line set bp on the beginning of method foo
         activate(iseq, :call, line)
       when events.include?(:RUBY_EVENT_LINE)
         activate(iseq, :line, line)

data/lib/debug/config.rb

@@ -65,16 +65,16 @@ module DEBUGGER__
       o.separator ''
 
       o.separator 'Debug console mode:'
-      o.on('-n', '--nonstop', 'Do not stop at the beggining of the script.') do
+      o.on('-n', '--nonstop', 'Do not stop at the beginning of the script.') do
         config[:nonstop] = '1'
       end
 
-      o.on('-e [COMMAND]', 'execute debug command at the beggining of the script.') do |cmd|
+      o.on('-e [COMMAND]', 'execute debug command at the beginning of the script.') do |cmd|
         config[:commands] ||= ''
         config[:commands] << cmd + ';;'
       end
 
-      o.on('-O', '--open', 'Start debuggee with opning the debagger port.',
+      o.on('-O', '--open', 'Start debuggee with opening the debugger port.',
                            'If TCP/IP options are not given,',
                            'a UNIX domain socket will be used.') do
         config[:remote] = true
@@ -109,7 +109,7 @@ module DEBUGGER__
       o.separator "  #{' ' * $0.size}            debugger connection, list possible debuggee names."
       o.separator "  '#{$0} -A path' tries to connect via UNIX domain socket with given path name."
       o.separator "  '#{$0} -A port' tries to connect localhost:port via TCP/IP."
-      o.separator "  '#{$0} -A host port' tris to connect host:port via TCP/IP."
+      o.separator "  '#{$0} -A host port' tries to connect host:port via TCP/IP."
     end
 
     opt.parse!(argv)

data/lib/debug/session.rb

@@ -4,7 +4,7 @@
                          :has_return_value, :return_value, :show_line)
 end
 
-require_relative 'debug.so'
+require "debug/debug"
 
 require_relative 'source_repository'
 require_relative 'breakpoint'
@@ -373,7 +373,7 @@ module DEBUGGER__
 
       # * `edit`
       #   * Open the current file on the editor (use `EDITOR` environment variable).
-      #   * Note that editted file will not be reloaded.
+      #   * Note that edited file will not be reloaded.
       # * `edit <file>`
       #   * Open <file> on the editor.
       when 'edit'
@@ -461,7 +461,7 @@ module DEBUGGER__
       # * `f[rame]`
       #   * Show current frame.
       # * `f[rame] <framenum>`
-      #   * Specify frame. Evaluation are run on this frame environement.
+      #   * Specify frame. Evaluation are run on this frame environment.
       when 'frame', 'f'
         @tc << [:frame, :set, arg]
 

data/lib/debug/version.rb

@@ -1,3 +1,3 @@
 module DEBUGGER__
-  VERSION = "1.0.0.beta1"
+  VERSION = "1.0.0.beta2"
 end

data/misc/README.md.erb

@@ -74,7 +74,7 @@ $ ruby target.rb
 ```
 
 When you run the program with the debug console, you will see the debug console prompt `(rdbg)`.
-The debuggee program (`target.rb`) is suspended at the beggining of `target.rb`.
+The debuggee program (`target.rb`) is suspended at the beginning of `target.rb`.
 
 You can type any debugger's command described bellow. "c" or "continue" resume the debuggee program.
 You can suspend the debuggee program and show the debug console with `Ctrl-C`.
@@ -137,7 +137,7 @@ $ rdbg  ~/src/rb/target.rb
  b => 2
  c => 3
 
-(rdbg) c                                                # Contineu the program ("c" is a short name of "continue")
+(rdbg) c                                                # Continue the program ("c" is a short name of "continue")
 [6]
 ```
 
@@ -173,12 +173,12 @@ Debugger can attach via UNIX domain socket (/home/ko1/.ruby-debug-sock/ruby-debu
 ```
 
 It runs target.rb and accept debugger connection within UNIX domain socket.
-The debuggee process waits for debugger connection at the beggining of `target.rb` like that:
+The debuggee process waits for debugger connection at the beginning of `target.rb` like that:
 
 ```
 $ rdbg -O ~/src/rb/target.rb
 DEBUGGER: Debugger can attach via UNIX domain socket (/home/ko1/.ruby-debug-sock/ruby-debug-ko1-29828)
-DEBUGGER: wait for debuger connection...
+DEBUGGER: wait for debugger connection...
 ```
 
 You can attach the program with the following command:
@@ -204,7 +204,7 @@ and you can input any debug commands. `c` (or `continue`) continues the debuggee
 You can detach the debugger from the debugger process with `quit` command.
 You can re-connect to the debuggee process by `rdbg -A` command again, and the debuggee process suspends the execution (and debugger can input any debug commands).
 
-If you don't want to stop the debuggee process at the beggining of debuggee process (`target.rb`), you can use the fowllowings to specify "non-stop" option.
+If you don't want to stop the debuggee process at the beginning of debuggee process (`target.rb`), you can use the following to specify "non-stop" option.
 
 * Use `rdbg -n` option
 * Set the environment variable `RUBY_DEBUG_NONSTOP=1`
@@ -282,7 +282,7 @@ $ rdbg --attach hostname 12345
 
 If there are `.rdbgrc` files are there at the current directory and the home directory, files are loaded as initial scripts which contains debugger commands. `RUBY_DEBUG_INIT_SCRIPT` environment variable can specify the initial script file.
 
-Initial scripts are evaluted at the first suspend timing (generally, it is the beggining of the target script). For example, you can set break points with `break file:123`.
+Initial scripts are evaluated at the first suspend timing (generally, it is the beginning of the target script). For example, you can set break points with `break file:123`.
 
 If there are `.rdbgrc.rb` files at the current directory and the home directory, files are loaded as a ruby script at the initializing timing.
 
@@ -290,7 +290,7 @@ If there are `.rdbgrc.rb` files at the current directory and the home directory,
 
 You can control debuggee's behavior with environment variables:
 
-* `RUBY_DEBUG_NONSTOP`: 1 for nonstop at the beggining of program.
+* `RUBY_DEBUG_NONSTOP`: 1 for nonstop at the beginning of program.
 * `RUBY_DEBUG_INIT_SCRIPT`: Initial script path loaded at the first stop.
 * `RUBY_DEBUG_COMMANDS`: Debug commands invoked at the first stop. Commands should be separated by ';;'.
 * `RUBY_DEBUG_SHOW_SRC_LINES`: Show n lines source code on breakpoint (default: 10 lines).
@@ -308,7 +308,7 @@ You can control debuggee's behavior with environment variables:
 * [debug command compare sheet - Google Sheets](https://docs.google.com/spreadsheets/d/1TlmmUDsvwK4sSIyoMv-io52BUUz__R5wpu-ComXlsw0/edit?usp=sharing)
 
 You can use the following debug commands. Each command should be written in 1 line.
-The `[...]` notation means this part can be elimiante. For example, `s[tep]` means `s` or `step` are valid command. `ste` is not valid.
+The `[...]` notation means this part can be eliminate. For example, `s[tep]` means `s` or `step` are valid command. `ste` is not valid.
 The `<...>` notation means the argument.
 
 <%= DEBUGGER__.help %>
@@ -322,4 +322,3 @@ The `<...>` notation means the argument.
 # Contributing
 
 Bug reports and pull requests are welcome on GitHub at https://github.com/ruby/debug.
-

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: debug
 version: !ruby/object:Gem::Version
-  version: 1.0.0.beta1
+  version: 1.0.0.beta2
 platform: ruby
 authors:
 - Koichi Sasada
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-05-07 00:00:00.000000000 Z
+date: 2021-05-10 00:00:00.000000000 Z
 dependencies: []
 description: Debugging functionality for Ruby. This is completely rewritten debug.rb
   which was contained by the encient Ruby versions.