[Bashdb-devel] bash 3.0

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

bash 3.0 is in alpha (or maybe it's beta by now). It has most of the
debugging support from this project, although I'm not certain it has
all of it.

The reason I'm not certain is just that a lot of stuff has been moved
around. What is "set -o fntrace" or "set -d" in rebash is in bash 3.0
"set -o functrace" or "set -T". You have to add "shopt -s extdebug" in
bash 3.0 to get any sort of debugging.

And in the code various declarations have been moved around or renamed
slightly: "the_printed_command_sans_trap" is now
"the_printed_command_except_trap".

Where I put: 
  subshell_level++;
  USE_VAR(user_subshell);
  USE_VAR(invert);
  USE_VAR(tcom);
  USE_VAR(asynchronous);

is in bash 3.0:

  USE_VAR(user_subshell);
  USE_VAR(invert);
  USE_VAR(tcom);
  USE_VAR(asynchronous);

  subshell_level++;

Some things I'm sure are improvements. Most of these things however,
probably semantically don't amount to much. Renaming
"the_printed_cmmand_sans_trap" I'm pretty sure doesn't change things
semantically, but I'm hard pressed to understand if there is a
semantic difference is in moving subshell_level above.

So of course, I rely on the regression tests, and although most of
these work in bash 3.0 not all do, notably those which fail show
what the upcoming command to be executed is which is used when there
are multiple statements on a line.  (I wrote Chet Ramey on this but
haven't received any comment.)

Omissions to me that are of some concern me are those made by other
folks such as to the auto stuff that done't appear in bash 3.0. The
project in contrast to bash 3.0 was intended as a vehicle whereby
others can find something they want changed discuss and fix and I
don't want to discourage that.

So here's what I'm thinking of doing. Create a split in the CVS tree
for bash 3.0 since there are just lots of changes and 2.05b and 3.0
can't be compatible from the debugger standpoint. For bash 3.0, the
debugger part I guess I'd try to have work both in bash 3.0 alpha and
in whatever additions we currently do and might have.

The good news is that bash 3.0 will have debugger support built
in. Will vanila bash have all of what's there? Don't know.

I welcome thoughts, comments, advice on how to proceed.