Recent changes to wiki

Discussion for Home page

Rocky Bernstein — Mon, 15 Dec 2014 00:31:00 -0000

I'm sorry I didn't see this sooner. Probably if this were filed under support requests or bugs I might have gotten a notification. Let's move discussion there if you are still interested.

Yes, probably the debugger is not finding the bulk of the code library and the install is supposed to make sure it gets this right. In the bashdb script look for variable _Dbg_libdir and see what directory that points to and make sure that is there.

Cool Commands modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 14:56:43 -0000

--- v3
+++ v4
@@ -10,7 +10,7 @@

 The debugger has a mode where anything you type into the debugger that recognized as a debugger command is automatically evaluated as bash code. The way the debugger determines if something is a debugger command is by looking up the first blank-delimited token in a command table and failing to find anything there, in an alias table. Aliases are customizable. (See the help for `alias` and  `unalias`.) Commands are not once they are added. 

-When this mode is set, if what you type is erroneous the corresponding zsh error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a bash command. 
+When this mode is set, if what you type is erroneous the corresponding bash error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a bash command. 

     :::bash
     $ bashdb /etc/init.d/apparmor status

Cool Commands modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 14:56:17 -0000

--- v2
+++ v3
@@ -10,7 +10,7 @@

 The debugger has a mode where anything you type into the debugger that recognized as a debugger command is automatically evaluated as bash code. The way the debugger determines if something is a debugger command is by looking up the first blank-delimited token in a command table and failing to find anything there, in an alias table. Aliases are customizable. (See the help for `alias` and  `unalias`.) Commands are not once they are added. 

-When this mode is set, if what you type is erroneous the corresponding zsh error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a zsh command. 
+When this mode is set, if what you type is erroneous the corresponding zsh error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a bash command. 

     :::bash
     $ bashdb /etc/init.d/apparmor status

Cool Commands modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 14:55:36 -0000

--- v1
+++ v2
@@ -8,7 +8,7 @@

 ## Auto Evaluation

-The debugger has a mode where anything you type into the debugger that recognized as a debugger command is automatically evaluated as zsh code. The way the debugger determines if something is a debugger command is by looking up the first blank-delimited token in a command table and failing to find anything there, in an alias table. Aliases are customizable. (See the help for `alias` and  `unalias`.) Commands are not once they are added. 
+The debugger has a mode where anything you type into the debugger that recognized as a debugger command is automatically evaluated as bash code. The way the debugger determines if something is a debugger command is by looking up the first blank-delimited token in a command table and failing to find anything there, in an alias table. Aliases are customizable. (See the help for `alias` and  `unalias`.) Commands are not once they are added. 

 When this mode is set, if what you type is erroneous the corresponding zsh error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a zsh command.

Home modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 12:02:33 -0000

--- v6
+++ v7
@@ -6,7 +6,7 @@

 * [Evaluating the current source line before it runs](https://sourceforge.net/p/bashdb/wiki/Evaluating%20the%20current%20source%20line%20before%20it%20runs/)
 * [Nested Shell](https://sourceforge.net/p/bashdb/wiki/Nested%20Shell/)
-
+* [Other Cool Commands](https://sourceforge.net/p/bashdb/wiki/Cool%20Commands/)
 ##### Screenshot
 [[project_screenshots]]
 [[project_admins]]

Cool Commands modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 12:01:16 -0000

Here we list some of the cooler commands that you might not be familiar with.

Auto Evaluation

The debugger has a mode where anything you type into the debugger that recognized as a debugger command is automatically evaluated as zsh code. The way the debugger determines if something is a debugger command is by looking up the first blank-delimited token in a command table and failing to find anything there, in an alias table. Aliases are customizable. (See the help for alias and unalias.) Commands are not once they are added.

When this mode is set, if what you type is erroneous the corresponding zsh error message is displayed and this sometime might be confusing if what you thought you typed was a debugger command rather than a zsh command.

$ bashdb /etc/init.d/apparmor status
Copyright 2008, 2009, 2010, 2011 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/etc/init.d/apparmor:35):
. /etc/apparmor/functions
bashdb<1> lis 5
lis 5
** Undefined command "lis". Try "help".
bashdb<1> set autoeval on
set autoeval on
Evaluate unrecognized commands is on.
bashdb<2> lis 5
lis 5
/tmp/bashdb_eval_1713:2: command not found: lis
$? is 127
bashdb<3> list 5
list 5
  1:    #!/bin/sh
  2:    # ----------------------------------------------------------------------
  3:    #    Copyright (c) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007
  4:    #     NOVELL (All rights reserved)
  5:    #    Copyright (c) 2008, 2009 Canonical, Ltd.
  6:    #
  7:    #    This program is free software; you can redistribute it and/or
  8:    #    modify it under the terms of version 2 of the GNU General Public
  9:    #    License published by the Free Software Foundation.
 10:    #
bashdb<4>

Because of the above potential confustion and because entering commands to be evaluated can be distructive, this mode is turned off by default. However most non-novice users prefer to set this mode on.

Auto list

Normally only the source code line to be displayed is listed in stopping in the debugger. However it is possible to automatically list more context automatically on each stop. For this use set autoeval.

Here is a sample session:

$ bashdb hanoi.sh 
bashdb hanoi.sh 
zsh debugger, bashdb, release 0.07

Copyright 2008, 2009, 2010, 2011 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/hanoi.sh:6):
init () { if (( $tracing )) then _Dbg_set_linetrace=1 fi }
bashdb<1> set autolist on
set autolist on
Auto run of 'list' command is on.
bashdb<2> s
(/hanoi.sh:13):
hanoi () {
    typeset -i n=$1
    typeset -r a=$2
    typeset -r b=$3
    typeset -r c ...
  8:      if (( $tracing )) ; then
  9:        _Dbg_set_linetrace=1
 10:      fi
 11:    }
 12:    
 13: => hanoi() { 
 14:      typeset -i n=$1
 15:      # _Dbg_set_trace
 16:      typeset -r a=$2
 17:      typeset -r b=$3
bashdb<3> s
(/hanoi.sh:30):
typeset -i max=3
 25:           hanoi $n $c $b $a
 26:        fi
 27:      fi
 28:    }
 29:    
 30: => typeset -i max=3
 31:    typeset -i tracing=0
 32:    if [[ "$1" = 'trace' ]] ; then
 33:      if [[ -n $2 ]] ; then
 34:          abs_top_builddir=$2
bashdb<4> s
(/hanoi.sh:31):
typeset -i tracing=0
 26:        fi
 27:      fi
 28:    }
 29:    
 30:    typeset -i max=3
 31: => typeset -i tracing=0
 32:    if [[ "$1" = 'trace' ]] ; then
 33:      if [[ -n $2 ]] ; then
 34:          abs_top_builddir=$2
 35:      elif [[ -z $builddir ]] ; then

If you want to change the number of context lines use set listsize:

bashdb<5> set listsize 4
bashdb<6> step
(/hanoi.sh:32):
if [[ "$1" = 'trace' ]]
then
    if [[ -n $2 ]]
    then
        abs_top_builddir=$2 
     ...
 30:    typeset -i max=3
 31:    typeset -i tracing=0
 32: => if [[ "$1" = 'trace' ]] ; then
 33:      if [[ -n $2 ]] ; then
bashdb<7> step
(/hanoi.sh:32):
[[ "$1" = 'trace' ]]
 30:    typeset -i max=3
 31:    typeset -i tracing=0
 32: => if [[ "$1" = 'trace' ]] ; then
 33:      if [[ -n $2 ]] ; then
bashdb<9>

To be continued...

Home modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 03:22:07 -0000

--- v5
+++ v6
@@ -1,7 +1,6 @@
 We have source tarballs of debuggers for bash, python, zsh, ksh, GNU make 3.81 and Python.

-Most version control for many of these has been moved elsewhere, but we still have the *bash* repository here and that's what we use this wiki for.
-
+Version control, in git, for many of these has been moved elsewhere, but we still have the *bash* repository here. That's what we use this wiki for.

 Here is what we have so far for bash:

Nested Shell modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 03:20:54 -0000

--- v1
+++ v2
@@ -1,4 +1,4 @@
-lthough the debugger allows one to evaluate arbitrary _bash_ code using the debugger _eval_ command or the __set autoeval__ mode, sometimes you might prefer to work inside a _bash_ shell to see variables, experiment, issue commands (using the currently-set up environment), and even change variables and functions.
+Although the debugger allows one to evaluate arbitrary _bash_ code using the debugger _eval_ command or the __set autoeval__ mode, sometimes you might prefer to work inside a _bash_ shell to see variables, experiment, issue commands (using the currently-set up environment), and even change variables and functions.

 For this we, the debugger _shell_ command, enters a nested shell session. But before it does this, it saves out variable and function definitions in the current context of the running program. That way, you have access to those.

Nested Shell modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 03:20:29 -0000

lthough the debugger allows one to evaluate arbitrary bash code using the debugger eval command or the set autoeval mode, sometimes you might prefer to work inside a bash shell to see variables, experiment, issue commands (using the currently-set up environment), and even change variables and functions.

For this we, the debugger shell command, enters a nested shell session. But before it does this, it saves out variable and function definitions in the current context of the running program. That way, you have access to those.

This however creates a new problem: getting changes you make reflected back into the running program. Right now any variable you change can be flagged to have its value re-read when the shell exits. This is done using the save_var function inside the nested shell. save_var takes a list of variable names.

Here is an example session

bashdb /etc/init.d/apparmor status
bashdb debugger, release 0.9

Copyright 2008-2011, 2014 Rocky Bernstein
...
(/etc/init.d/apparmor:35):
. /etc/apparmor/functions
bashdb<1> s
(/etc/apparmor/functions:24):
PROFILES="/etc/apparmor.d"
bashdb<2> s
(/etc/apparmor/functions:25):
PARSER="/sbin/apparmor_parser"
bashdb<3> shell
bashdb $ typeset -p PROFILES
typeset PROFILES=/etc/apparmor.d
bashdb $ PROFILES='Hi, Mom!'
bashdb $ save_vars PROFILES
bashdb $  <EOF>
(/etc/apparmor/functions:25):
PARSER="/sbin/apparmor_parser"
bashdb<4> x PROFILES
typeset PROFILES='Hi, Mom!'
bashdb<5>

Note that inside the nested shell the we have set the prompt has been set to: bashdb $

Home modified by Rocky Bernstein

Rocky Bernstein — Sun, 14 Dec 2014 03:18:01 -0000

--- v4
+++ v5
@@ -6,6 +6,7 @@
 Here is what we have so far for bash:

 * [Evaluating the current source line before it runs](https://sourceforge.net/p/bashdb/wiki/Evaluating%20the%20current%20source%20line%20before%20it%20runs/)
+* [Nested Shell](https://sourceforge.net/p/bashdb/wiki/Nested%20Shell/)

 ##### Screenshot
 [[project_screenshots]]