[Bashdb-devel] -L option and DDD stop sign (Was: How can I debug called scripts?)

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

 > 1. I'm able to use ddd with bashdb by typing:
 > 
 >      ddd --bash build.sh
 > 
 >      ...but when I type:
 > 
 >      bashdb -L .  build.sh
 > 
 >      ...alone, as from the bashdb manual example, I
 > get the following error:
 > 
 >      bashdb: cannot read debugger file ./dbg-main.inc.
 >      bashdb: Perhaps bashdb is installed incorrectly.
 > 
 >      ...however, dbg-main.inc does exist in the
 > following 2 directories:
 > 
 > /home/rick/programs/bash-2.05b-debugger-0.36/debugger/dbg-main.inc
 > /usr/local/lib/bashdb/dbg-main.inc
 > 
 >  (Note: the first directory is the one in which I did
 > the build.) The file access attributes are:  -rw-r-r--
 > 1 root  root  for the file in /usr/local/lib/bashdb. I
 > executed the "make" steps as a regular user, and
 > switched to "su" for the "make install".

You don't understand the meaning of -L option. Perhaps the bashdb
manual wasn't clear, so I've expanded that section which is in CVS and
in HTML online. The relevant portions now read:

2.1.1. Command-line options for bashdb script 
  ...

  -L directory Set directory where debugger files reside to
  directory. The default location is ../lib/bashdb relative to the place
  that the bashdb script is located. For example if bashdb is located in
  /usr/local/bin/bashdb, the default library location will be
  /usr/local/lib/bashdb which may or may not exist. If it doesn't you'll
  get an error when you run bashdb. Only if the default location is
  incorrect, should you need to use the -L option.


1.1 A Sample BASH Debugger Session
  ...

  The command invocation uses the option "-L ." Here we assume that the
  bashdb script and the debugger files are in the same location. If you
  are running from the source code, this will be the case. However if
  bashdb has been installed this probably won't be true and here you
  probably don't need to use "-L ." Instead you would type simply bashdb
  fact.sh.

 > 
 > 2.  ddd breakpoint problem.
 > 
 > I am able to set a breakpoint in my script in ddd, but
 > the little "Stop Sign" is not displayed in the source
 > panel. The only way I can view breakpoints is to
 > select the menu item Source/Breakpoints...  Minor
 > problem, but still a bit bothersome.

Sorry, I don't know to change ddd so that it would handle this. You or
anyone else following this is welcome to suggest a change (or better
patches) to either the ddd source or the bashdb source.

Bash is not the only language that doesn't display a stop sign. I
tried with Perl and don't see it there either. 

Another way to view breakpoints is to type "L" or "show break" (the
former being the Perl debugger's corresponding command, and the latter
being gdb's corresponding command).