trepanning 0.1.6 → 1.93.32

data/README.textile

@@ -1,50 +0,0 @@
-A modular, testable debugger for MRI Ruby 1.9.2 or 1.9.3. A total rewrite of _ruby-debug_.
-
-__In order to use this debugger, you'll need a patched MRI Ruby 1.9.2 or 1.9.3 and some additional packages. See the "installation instructions.":https://github.com/rocky/rb-trepanning/wiki/How-to-Install-rb-trepanning__
-
-Right now this debugger is beta code.
-
-There is a "google group mailing list":http://groups.google.com/group/ruby-debugger for Ruby debuggers.
-
-If rb-trepanning is installed, here is how to run:
-
-bc.  trepan ruby-program [program]
-
-If your program needs options of its own:
-
-bc.  trepan -- ruby-program [program args...]
-
-If you want to run from the source tree you can do that too:
-
-bc.  cd place-where-trepan-is-installed:
- ./bin/trepan -- ruby-program [program args...]
-
-Running from inside _irb_:
-
-bc.  require 'trepanning' 
- Trepan.debug { your code }
-
-The return value from Trepan is the return value of the block, i.e. the final value in the block.
-
-You can run the same thing inside your Ruby program, but probably you don't want to give a block. Instead, you may want to have debugging start on the next statement in the code:
-
-bc.  require 'trepan' 
- Trepan.debug # Don't stop here...
- work # but stop here.
-
-The above is really shorthand for something like:
-
-bc.  $trepan = Trepan.new
- $trepan.debugger
-
-The global variable $trepan set holds debugger settings, such as "autolist" or "autoeval" settings and breakpoint information.
-
-Due to the line-event orientation in ruby-debug, it occasionally was convenient to add a synchronous stop in your program. I don't think that will be necessary here, but if you do call to the debugger at the point of the call rather than the subsequent stopping point, set opts[:immediate] to true. Example:
-
-bc.  # ... work, work, work 
- mydbg.debugger(:immediate=>true) # enter debugger here 
- # ... work, work, work
-
-There is extensive on-line help. Run "help" inside the debugger.
-
-

data/processor/command/help/examples.txt

@@ -1,16 +0,0 @@
-Command examples
-
-# This line does nothing. It is a comment. Useful in debugger command files.
-     # This line also does nothing. 
-s    # by default, this is an alias for the "step" command
-!s   # shows the value of variable "s".
-!!s  # Evaluates "!s" (or "not s"). The first ! is indicates evaluate.
- !s  # Same as above, since there is a space in column one.
-
-info program;; list # Runs two commands "info program" and "list"
-pr  "hi ;;-)"  # Syntax error since ;; splits the line and " is not closed.
-!puts "hi ;;-)" # One way to do the above.
-
-See also "macro" "alias", "irb", "set auto eval", "set auto irb", "set
-abbrev", "info macro", and "show" variants of the above "set"
-commands.

data/processor/command/help/filename.txt

@@ -1,40 +0,0 @@
-syntax for indicating a filename
-
-There are two ways you can give a file name:
-  - unadorned (without double-quotes) with possible escapes
-  - as a double-quoted string with possible escapes in the string
-
-Probably most of the time a file name will be specified in the first
-form, without using quotes. If the file name however has a space or a
-colon in it, escape that character with a backslash. Also, if you need
-to enter a backslash and the character followinng that is unlucky
-enough to be a colon, space, or backslash use two backslashes. Some
-examples:
-
-   irb.rb       => irb.rb
-   /tmp/irb.rb  =>  /tmp/irb.rb
-   C\:irb.rb    =>  C:irb.rb
-   C\:\irb.rb   =>  C:\irb.rb
-   C\:\\irb.rb  =>  C:\irb.rb  # Note: double slash not needed
-   \\new.rb    =>  \new.rb     # Note: double slash, or filename has newline
-   my\ file.rb  =>  my file.rb
-
-
-The quoted string is useful if you have a file name that contains
-several characters that normally confuse the debugger parser, notably
-a space, newline, or a colon. The quoted string starts with a double
-quote ("). Escape sequences are allowed inside the string to be able
-to enter tabs or newlines, or a double quote inside the string. The
-list of translations is as follows:
-   
-   \t => <tab>
-   \n => <newline>
-   \" => "
-   \\ => \
-
-Here are some examples of quoted filenames:
-
-  "This is a file with blanks.rb" => This is a file with blanks.rb
-  "/tmp/RubyProgram \"foo\".rb    => /tmp/RubyProgram "foo".rb
-  "/Ruby\nProgram.rb"             => /tmp/Ruby
-Program.rb

data/processor/command/help/location.txt

@@ -1,37 +0,0 @@
-syntax for source code locations; e.g. used "list" and "break"
-
-Locations are used to indicates places in the source code or the
-places in bytecode compiled from source code. Locations are used in
-the listing commands like "list" or "disassemble"; they are also used
-in "breakpoint" commands like "break", "tbreak" and "continue"
-
-A location is either some sort of "container" and a position inside
-that container. A container is either a file name or a method
-name. And a position is either a line number or a bytecode offset.
-Bytecode offsets are prefaced with an '@'. So 4 is a line number 4, but
-@4 is bytecode offset 4. 
-
-File names are distinguished from method names purely by semantic
-means.  That its "foo" (without the quotes) could conceivably be
-either a method or a file name. The debugger does a file check to see
-if "foo" is a file. 
-
-In gdb, locations are often given using a filename a colon and a line
-number. That is supported here are well. So myfile.rb:5 indicates line 5
-of file "myfile.rb". But since we also allow method names you can also use
-"gcd:5" to indicate line 5 of method "gcd". 
-
-Line numbers in methods are not relative to the beginning of the
-method but relative the beginning of source text that contains the
-method. This is also how Ruby stores line numbers for methods which
-are shown for example in a backtrace. So all of this hopefully will
-feel familiar and consistent. 
-
-Instead of using a colon to separate the container and the position,
-you can also use spacs. So "gcd 5" is the same as gcd:5. 
-
-If the filename has an embedded blank in it, you can indicate that by
-using a backslash escape. For example: "file\ with\ blanks.rb"
-
-
-

data/processor/command/help/suffixes.txt

@@ -1,17 +0,0 @@
-Command suffixes which have special meaning
-
-Some commands like "step", or "list" do different things when an
-alias to the command ends in a particular suffix like ">". 
-
-Here are a list of commands and the special suffixes:
-
-command   suffix
--------   ------
-list       >
-step       +,-,<,>
-next       +,-,<,> 
-quit       !
-kill       !
-eval       ?
-
-See help on the commands listed above for the specific meaning of the suffix.

data/processor/command/info_subcmd/registers_subcmd/dfp.rb

@@ -1,28 +0,0 @@
-# -*- coding: utf-8 -*-
-# Copyright (C) 2010 Rocky Bernstein <rockyb@rubyforge.net>
-require_relative '../../base/subsubcmd'
-require_relative 'helper'
-
-class Trepan::Subcommand::InfoRegistersDfp < Trepan::SubSubcommand
-  unless defined?(HELP)
-    Trepanning::SubSubcommand.set_name_prefix(__FILE__, self)
-    HELP         = 'Show the value of the VM dynamic frame pointer (DFP)'
-    MIN_ABBREV   = 'df'.size
-    NEED_STACK   = true
-  end
-
-  include Registers
-  def run(args)
-    register_array_index(PREFIX[-1], args[0])
-  end
-end
-
-if __FILE__ == $0
-  # Demo it.
-  require_relative '../../../mock'
-  require_relative '../registers'
-  cmd = MockDebugger::subsub_setup(Trepan::SubSubcommand::InfoRegisters,
-                                   Trepan::SubSubcommand::InfoRegistersDfp,
-                                   false)
-  cmd.run(['0'])
-end

data/processor/command/info_subcmd/registers_subcmd/lfp.rb

@@ -1,47 +0,0 @@
-# -*- coding: utf-8 -*-
-# Copyright (C) 2010, 2011 Rocky Bernstein <rockyb@rubyforge.net>
-require_relative '../../base/subsubcmd'
-require_relative 'helper'
-
-class Trepan::Subcommand::InfoRegistersLfp < Trepan::SubSubcommand
-  unless defined?(HELP)
-    Trepanning::SubSubcommand.set_name_prefix(__FILE__, self)
-    HELP = <<EOH
-#{CMD} NUMBER
-
-Show the value of the VM local frame pointer (LFP).
-When a local variable is defined for the first time, this stack
-is pushed and the value for local variable is assigned to this stack entry.
-
-See also "info register sp".'
-EOH
-
-    MIN_ABBREV   = 'lf'.size
-    MIN_ARGS     = 1
-    MAX_ARGS     = 1
-    NEED_STACK   = true
-    SHORT_HELP   = "Show the value of the VM local frame pointer (LFP)."
-  end
-
-  include Registers
-  def run(args)
-    frame = @proc.frame
-    if 'CFUNC' == frame.type
-      msg "local_name not available for C function"
-    else
-      iseq = frame.iseq
-      index = register_array_index(PREFIX[-1], args[0], iseq.local_size-1)
-      msg("local_name(%d)=%s" % [index, iseq.local_name(index)]) if index
-    end
-  end
-end
-
-if __FILE__ == $0
-  # Demo it.
-  require_relative '../../../mock'
-  require_relative '../registers'
-  cmd = MockDebugger::subsub_setup(Trepan::SubSubcommand::InfoRegisters,
-                                   Trepan::SubSubcommand::InfoRegistersLfp,
-                                   false)
-  cmd.run([])
-end

data/processor/command/nocache.rb

@@ -1,32 +0,0 @@
-# -*- coding: utf-8 -*-
-# Copyright (C) 2010, 2011 Rocky Bernstein <rockyb@rubyforge.net>
-require_relative '../command'
-class Trepan::Command::NoCacheCommand < Trepan::Command
-
-  unless defined?(HELP)
-    HELP         = "Remove getinlinecache instructions from instruction sequence."
-
-    CATEGORY     = 'running'
-    MAX_ARGS     = 0   # Need at most this many
-    NAME         = File.basename(__FILE__, '.rb')
-    NEED_STACK   = true
-    SHORT_HELP   = 'Remove getinlinecache instructions from instruction sequence.'
-
-  end
-
-  # This method runs the command
-  def run(args)
-    if @proc.frame.iseq
-      puts @proc.frame.iseq.disassemble
-      count = @proc.frame.iseq.killcache
-      msg "%d locations removed" % count
-      # puts @proc.frame.iseq.disassemble
-    end
-  end
-end
-
-if __FILE__ == $0
-  require_relative '../mock'
-  dbgr, cmd = MockDebugger::setup
-  cmd.run([cmd.name])
-end

data/processor/command/parsetree.rb

@@ -1,56 +0,0 @@
-# -*- coding: utf-8 -*-
-# Copyright (C) 2011 Rocky Bernstein <rockyb@rubyforge.net>
-begin
-  require 'rubygems'
-  require 'parse_tree'
-  require_relative '../command'
-  require_relative '../../app/cmd_parse'
-  class Trepan::Command::ParseTreeCommand < Trepan::Command
-    
-    unless defined?(HELP)
-      NAME = File.basename(__FILE__, '.rb')
-      HELP = <<-HELP
-#{NAME}
-#{NAME}  method
-
-In the first form, print a ParseTree S-expression of the current 
-class. 
-In the second form, preint a ParseTree S-expression of the current method.
-In the third form print a ParseTree S-expression of CLASS.
-In the fourth form, print a ParseTree S-expression of the given method.
-HELP
-
-    # ALIASES       = %w(p)
-      CATEGORY      = 'data'
-      SHORT_HELP    = 'PrettyPrint a ParseTree S-expression'
-    end
-    
-    def run(args)
-      @processor ||= ParseTree19.new(false)
-      meth = nil
-      case args.size
-      when 1
-        method_name = @proc.frame.method
-      when 2
-        method_name = args[1]
-      else
-        errmsg 'Expecting a method name'
-        return
-      end
-      meth = Trepan::CmdParser.meth_for_string(method_name, @proc.frame.binding)
-      if meth and meth.kind_of?(Method)
-        msg @processor.parse_tree_for_method(meth, true).pretty_inspect
-      end
-    end
-
-    if __FILE__ == $0
-      require 'pp'
-      require_relative '../mock'
-      dbgr, cmd = MockDebugger::setup
-      cmd.proc.frame.instance_variable_set('@binding', TOPLEVEL_BINDING)
-      cmd.run([cmd.name, 'FileUtils.rm'])
-    end
-    
-  end
-rescue LoadError
-end