[Bashdb-devel] Re: How can I debug called scripts? (Rick Horowitz)

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

bas...@li... writes:
 > Is there a way to continue debugging into a secondary
 > shell script that is called by the main script? When I
 > tried debugging the main script, I was able to
 > single-step through the script (using DDD with bashdb)
 > - worked great. But the script calls another script
 > and bashdb simply ran that script. Is there a way to
 > cause the second script to also run in the debugger?

You can do this with the "debug" debugger command: 

 deb [script]    Set up [script] for debugging. If no script is given, take
                 the script name from the command to be executed.
                 Long command name: debug.

You won't find a button for this in ddd -- probably the only other
place where it might make sense is for Perl. When you debug into or
out of a script in ddd, the display I think is messed up for a line. I
don't know of a way to force ddd to refresh the display. As far as I
can tell ddd development has been dead for 2 years.

If "debug" is something you want to create a custom button for, you
can do so via the menus:

  Commands
    Edit Buttons
      uncheck enable supported buttons only
      in text box add the word "debug".

- - - 

By the way, in testing the above I tried debugging this this on a
script which contained the "~" character. The current bashdb can't
handle this but I've just changed the CVS version to fix this. If
associative arrays are added to bash or this is ported to ksh, this
kind of adding funny characters won't be a problem since untranslated
filenames could used as indexes.