bashdb-announce — List for announcement of the new release

[Bashdb-announce] bashdb 4.3-0.9 released a while ago

[Rocky B. <ro...@gn...>]

Was putting out an announcement for an update to remake (based on version
4.1) and realized that I hadn't been posting changes to bashdb updates.

Last September I put out a release of bashdb that works with bash 4.3.

Sorry for the delayed announcement.

[Bashdb-announce] Release 4.3-0.9 out

[Rocky B. <ro...@gn...>]

This release addresses changes to bash since 4.2.

One incompatible change to note is that previously I had mixed up "up" and
"down" with respect to the way gdb handles this. This has been corrected.
Following gdb 'u' is no longer an alias for up and 'd' is now 'delete' not
'down'.

[Bashdb-announce] Release 4.2-0.7 out

[Rocky B. <ro...@gn...>]

A new release is out. The first three items from the NEWS file I think
are cool.

I don' t have a bashdb wiki (and should probably create one), but I
did create some wiki entries for the
related debugger zshdb which give some feel of the first two features. See

https://github.com/rocky/zshdb/wiki/Terminal-Colors
https://github.com/rocky/zshdb/wiki/Evaluating-the-current-source-line-before-it-runs
https://github.com/rocky/zshdb/wiki/Nested-Shell


- syntax coloring if the Python pygments package installed (and
  --highlight option used)
- easy way to evaluate the current source line or expression inside
  the source line (debugger commands "eval" and "eval?")
- ability to go into a nested shell but keeping existing variables and
  functions set. (debugger command "shell") With this, one needs...
- ability to save variables to an outer shell ("set_vars" function
  inside the interactive shell)
- ability to save values from inside a subshell to the outer shell
  (debugger command "export")
- add --init-file (akin to same option in bash) to have bash code
  sourced

[Bashdb-announce] bashdb 4.2-0.06 and zshdb 0.6

[Rocky B. <ro...@gn...>]

New bashdb and zshdb debuggers releases have been made.

For bashdb:

- Debugger "list" command carries on where we last left off and
  centers around a line unless given a start and end line number. l> added.
- Fixed --no-init (--nx, -n) option
- Fixed to work on bash version 4.2
- Reorganized command-processing code to simplify it, make it more dynamic,
  and allow for better expansion increasing DRYness. As a result
  some short abbreviations of commands have been dropped. Use "alias"
  to add back any that you want.
- Make "display" command more like gdb. Note this is an incompatible change.
  Left to do is to start indexing from 1.
- Emacs lisp code has been removed. Please multi-debugger code from
  http://github.com/rocky/emacs-dbgr instead.
- Numerous little bugs fixed.

For zshdb:



- Debugger "list" command carries on where we last left off. By default
  it centers around the selected line. Use list> to force starting at the
line.
- Reorganized command-processing code to simplify it, make it more dynamic,
  and allow for better expansion increasing DRYness. As a result
  some short abbreviations of commands have been dropped. Use "alias"
  to add back any that you want.

[Bashdb-announce] bashdb and zshdb releases 4.1-0.5 and 0.5

[Rocky B. <ro...@gn...>]

New bashdb and zshdb debuggers releases have been made. Changes are small,
and include bug fixes and code reorganization. The debugger "set autolist"
has been  added.

For zshdb, the "action" command has been added. (bashdb has had this for a
while.)

[Bashdb-announce] bashdb 4.1-0.4 for bash 4.1

[Rocky B. <ro...@gn...>]

bashdb 4.1-0.4 has just been put on sourceforge
https://sourceforge.net/projects/bashdb/files/  .

Once again there has been a somewhat largish rewrite to use bash 4.x's
associative arrays and bash 4.1's left-hand-side file descriptor assignment.
The latter I think will improve reliability in debugging configure scripts
(and things like that) which open a number of file descriptors and redirect
standard input, error, and output.

Many thanks to Chet Ramey for adding that requested feature.

[Bashdb-announce] bashdb 4.0-0.1 released

[R. B. <ro...@pa...>]

This major rewrite and reorganization of code has numerous bugfixes and has been tested on bash 3.1 and 4.0 alpha. With the introduction of a simple debugger command alias mechanism, there are some incompatibilities. Command aliasing of short commands is no longer hard-wired. New commands of note are "set autoeval" and "step+", taken from ruby-debug. Emacs support has been greatly improved. Long option command-processing is guaranteed. 

[Bashdb-announce] bashdb-3.1-0.09 released

[R. B. <ro...@pa...>]

Also works on bash 3.2. Most of the changes are small bugfixes from
over the year.

[Bashdb-announce] bashdb-3.1-0.08 released

[R. B. <ro...@pa...>]

Mostly minor fixes. From the NEWS

 - Files coming from function line-specifications should be read in.
   Debian Bug #40336

 - add a gdb-like "load" command to force reading in a file.

 - negative numbers allowed in "frame" (and "up" and "down") commands. 
   In particular "frame -1" refers to the oldest frame.  Some
   refactoring of this code.

 - Note setting $PS4 in doc.

 - Help, manual-page and documentation fixes.

[Bashdb-announce] bashdb-3.1-0.07 and bashdb-3.00-0.05 released

[R. B. <ro...@pa...>]

As always, thanks to everyone who helped with the release.

Changes to bashdb-3.1-0.07

  This release adds the debugger commands "signal", "kill", and
  "quit"; "continue" allows an optional line-specification
  argument. This version works on bash 3.1 and 3.2, and changes have
  been made to facilitate building on Cygwin. Some bugs have been
  fixed and documentation updated.

Changes to bashdb-3.00-0.05

  Some bugs were fixed and some of the features from the 3.1 branch
  (e.g. the debugger commands "signal", "complete", "cd", and pwd")
  were merged in.

[Bashdb-announce] bashdb 3.1-0.06 released

[R. B. <ro...@pa...>]

There have been a number of small put important changes. Basically
working on extending the Python debugger has helped this project out
and I've tried to make the code bases be more alike.

>From the NEWS: 

- runs debugger commands at a specified breakpoint
  gdb 'commands' command: 
  

- Add gdb 'info program'. (Shows program status)

- Add ability to invoke from inside a running program rather than
  at the outset (set_trace)

- Add a better line tracing:
   * shows bash nesting, 
   * bash subshell nesting
   * function nesting
   * source line preserving initial indentation

- Add line tracing command-line option in bashdb: -X, and long option --trace

- add ability to turn on and off line tracing from inside a program

- Revise sample sessions in bashdb document

- Sourcing a debugger command file now prints the 
  command before executing it.

- Executing a string (option -c or --command) shows the command
  to be run in the call stack.

- Attempt to get documentation on GNU Emacs section in order. Describe
  bashdbtrack.

- Go over documentation yet again.

[Bashdb-announce] bashdb 3.1-0.06 released

[R. B. <ro...@pa...>]

There have been a number of small put important changes. Basically
working on extending the Python debugger has helped this project out
and I've tried to make the code bases be more alike.

>From the NEWS: 

- runs debugger commands at a specified breakpoint
  gdb 'commands' command: 
  

- Add gdb 'info program'. (Shows program status)

- Add ability to invoke from inside a running program rather than
  at the outset (set_trace)

- Add a better line tracing:
   * shows bash nesting, 
   * bash subshell nesting
   * function nesting
   * source line preserving initial indentation

- Add line tracing command-line option in bashdb: -X, and long option --trace

- add ability to turn on and off line tracing from inside a program

- Revise sample sessions in bashdb document

- Sourcing a debugger command file now prints the 
  command before executing it.

- Executing a string (option -c or --command) shows the command
  to be run in the call stack.

- Attempt to get documentation on GNU Emacs section in order. Describe
  bashdbtrack.

- Go over documentation yet again.

[Bashdb-announce] bashdb for bash 3.0 available

[R. B. <ro...@pa...>]

A port of the bashdb debugger from the 2.05b series now works for bash
3.0.

An optional but useful patch for bash 3.0 is needed to get the
BASH_COMMAND (the command to be executed) working.

Other than that, there is one slight regression in function over the
bash 2.05b debugger in that in the standalone bashdb script, the
parameters given to the script no longer appear in a traceback. They
do however appear when running via "bash --debugger"

The source can be obtained here: 
http://prdownloads.sourceforge.net/bashdb/bashdb-3.00-0.01.tar.gz?download

[Bashdb-announce] BASH with debug (bashdb) 0.43 available

[R. B. <ro...@pa...>]

What's changed in version 0.43
- Add "file" command
- Expand bash.1 to include more rebash extensions, e.g. variable names
- Improve documentation
- Fix bug listing line numbers and restarting when debugged program has
  done a cd. Save initial cwd.
- don't install gud unless we have emacs version 21.0 to 21.3.
- reduce spurious warnings in bash and rebash regression tests.
- test for null filename in reading in source.
- Lots of gcc -Wall compiler warnings removed. There were some potential
  uses of uninitalized variables (if not one outright bug).
- fix mis-configuration for OSs that have both GNU gettext and one in libc

[Bashdb-announce] rebash 0.42 released

[R. B. <ro...@pa...>]

Change from version 0.41: 

- Autostuff improvements
- fixes to make Cygwin, OS X and AIX builds
- configurable package and executable names
- Allow modification the philosophical parts the bashdb reference
  manual to placate Matthias Klose and presumably Debian folks
- Bug: a comment line in the history was taken as a timestamp and we 
  dumped core. Non-timestamp comment lines should appear in the history now.
- Bug: was not expanding source filename in debugger the correct way.
- Mention HISTTIMEFORMAT in bash.1
- Add bashdb manual page.
- Changes to allow building outside of source tree.
- Add Debian bash 2.05b patches provided by Matthias Klose.