byebug 2.1.0 → 2.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 16eb83030dd348fff8d681d7fc1cb7afdbbcfe93
-  data.tar.gz: c22e24de059a48c698e5fa8a68adef55902cfbb2
+  metadata.gz: 8ce377f1e91c98824d4b2f13186abca18ae9916f
+  data.tar.gz: e8225ad23bd321ce9fa0373a2d30fb7b6fa9fad8
 SHA512:
-  metadata.gz: 06281b839a4a394cbf7eb4c1ea708fce8c2ba5754b0248b716e424a01843391da5e11545c255b9e6fa221f3c9c2d095fa3272150663b1044340767d6d1eb7bd3
-  data.tar.gz: f728e9648771220b3312224d8d31def9cfc9d1e6ad756ba6beff701a15ae434635378fc68b2c7f613cd939459afff9bc9fbc2ba44d10e32b68c514f3eeda24cb
+  metadata.gz: e24e6c9e24efbd1e88f298c5a091af7348ad679f2ef2945b4b5e46ad3db2ea7da123dc0bc41d3e4696bd68a8b371694266480a16bda074f7b6de17188e926013
+  data.tar.gz: a6e0cda3871f5555ea1ab7b025a1c47af188573172d83e87eb5966bf091419cb2a7e16bcc0de65abce2677b11475d585ed922044838c7b4a4969bf6e5e4e3b45

data/CHANGELOG.md

@@ -1,3 +1,8 @@
+# 2.1.1
+
+* Fix bug when debugging code inside '-e' flag
+
+
 # 2.1.0
 
 * Fix bug in remote debugging display

data/lib/byebug/processor.rb

@@ -46,7 +46,7 @@ module Byebug
     # are working remotely and want to change the basename. Or we are eliding
     # filenames.
     def self.canonic_file(filename)
-      return '(nil)' if not filename
+      return filename if ['(irb)', '-e'].include?(filename)
 
       # For now we want resolved filenames
       if Command.settings[:basename]
@@ -145,7 +145,7 @@ module Byebug
         state = State.new(event_cmds, context, @display, file, @interface, line)
 
         # Change default when in irb or code included in command line
-        Command.settings[:autolist] = 0 if file == '(irb)' or file == '-e'
+        Command.settings[:autolist] = 0 if ['(irb)', '-e'].include?(file)
 
         # Bind commands to the current state.
         commands = event_cmds.map{|cmd| cmd.new(state)}
@@ -262,6 +262,7 @@ module Byebug
           loc = "#{CommandProcessor.canonic_file(@file)} @ #{@line}\n"
           loc += "#{Byebug.line_at(@file, @line)}\n" unless
             ['(irb)', '-e'].include? @file
+          loc
         end
       end
 

data/lib/byebug/version.rb

@@ -1,3 +1,3 @@
 module Byebug
-  VERSION = '2.1.0'
+  VERSION = '2.1.1'
 end

data/old_doc/byebug.1

@@ -185,9 +185,6 @@ version number.
 .B \-\-nx
 Don't execute commands found in any initialization files, e.g. .byebugrc.
 .TP
-.B \-\-keep-frame-binding
-Keep frame bindings.
-.TP
 .B \-\-script=FILE
 Name of the script file to run
 .TP

data/old_doc/byebug.texi

@@ -919,7 +919,6 @@ Usage: byebug [options] <script.rb> -- <script.rb parameters>
 Options:
     -d, --debug                Set $DEBUG=true
     -I, --include PATH         Add PATH to $LOAD_PATH
-        --keep-frame-binding   Keep frame bindings
     -m, --post-mortem          Activate post-mortem mode
         --no-quit              Do not quit when script finishes
         --no-stop              Do not stop when script is loaded
@@ -976,33 +975,6 @@ Set @code{$DEBUG} to @code{true}. This option is compatible with Ruby's.
 @cindex @option{--include} @var{PATH}
 Add @var{PATH} to @code{$LOAD_PATH}
 
-@item --keep-frame-binding
-@cindex @option{--keep-frame-binding}
-Bindings are used to set the proper environment in evaluating expressions inside
-byebug. Under normal circumstances, I don't believe most people will ever need
-this option.
-
-By default, byebug doesn't create a binding object for each frame when the frame
-is created, i.e. when a call is performed. Creating a binding is an expensive
-operation and has been a major source of performance problems.
-
-Instead, byebug creates a binding when there is a need to evaluate expressions.
-The artificial binding that is created might be different from the real one. In
-particular, in performing constant and module name resolution.
-
-However it's still possible to restore the old, slower behavior by using this
-option or by setting @code{Byebug.keep_frame_binding = true}. There are two
-possibilities for which you might want to use this option.
-
-First, if you think there's a bug in the evaluation of variables, you might want
-to set this to see if this corrects things.
-
-Second, since the internal structures that are used here @code{FRAME} and
-@code{SCOPE} are not part of the Ruby specification, it is possible they can
-change with newer releases; so here this option this may offer a remedy. (But
-you'll probably also have to hack the C code since it's likely under this
-scenario that byebug will no longer compile.)
-
 @item -m | --post-mortem
 @cindex @option{-m}
 @cindex @option{--post-mortem}

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: byebug
 version: !ruby/object:Gem::Version
-  version: 2.1.0
+  version: 2.1.1
 platform: ruby
 authors:
 - David Rodriguez
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-09-08 00:00:00.000000000 Z
+date: 2013-09-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: columnize
@@ -245,7 +245,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.3
+rubygems_version: 2.0.8
 signing_key: 
 specification_version: 4
 summary: Ruby 2.0 fast debugger - base + cli