[Bashdb-devel] Releases to bash 3.1 and 3.0 debuggers around Dec 10, 2006

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

Recently I've needed to use the debugger on a computer that was
running bash 3.0 and ran into a bug in the debugger. It is also
present in the 3.1 debugger as well.

It's been a while since I had a computer running bash 3.0 so it should
be no surprise that the version of the debugger is a little bit behind
the debugger for 3.1 in terms of features. So I've spent a little time
getting that more closely synchronized to the 3.0 and 3.1 debuggers to
a little to the benefit of both.

Of late, I've been making releases on a friend's birthday and the next
one coming up is December 10th. If you have a chance to try the
tarballs that is helpful. The candidate tarballs are in
  http://bashdb.sf.net/bashdb-3.1-0.07cvs.tar.gz and
  http://bashdb.sf.net/bashdb-3.00-0.05cvs.tar.gz

Here are the relevent portions of NEWS for each: 

Version 3.00 0.05
12-10-06

- Add "signal" and "complete" debugger commands

- Fix bug in tracking parameters $1, $2, etc

- Add --enable-getopt option to disable GNU getopt for systems that have 
  non-GNU getopt like NetBSD

- Add cd and pwd

- Allow an optional line-spec on "continue" debugger command.

- Fix bug in displaying watch when variable doesn't exist

- Add Emacs bashdbtrack to track debugging in an Emacs comint shell


Version 3.1 0.07cvs
2006-12-10

- Add gdb-like "signal" command

- Add "kill" command for those cases where "quit" doesn't work.

- Add mechanism to set up signal handlers so debugger is entered,
  or we just print the signal. 

- document how to do call line tracing from within a program, i.e.
  like the above signal handling setup, the debugger is not entered
  first.

- Allow an optional line-spec on "continue" debugger command.

- Add --enable-getopt option to disable GNU getopt for systems that have 
  non-GNU getopt like NetBSD

- Fix bug in tracking parameters $1, $2, etc

- Emacs interface bug fixes

- readarray builtin internal changes

- Document updates