bashdb-devel — Developer's discussion mailing list

[Bashdb-devel] Please try out bashdb-4.3-0.9rc1.tar.gz

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

I have put out a candidate release bashdb for bash 4.3 at
http://bashdb.sourceforge.net/bashdb-4.3-0.9rc1.tar.gz

Please try it out. I plan to release it in a couple of days unless people
report problems with this.

Thanks.

[Bashdb-devel] Test failed on CentOS 6.4

[Carl <bc...@gm...>]

===================================================
1 of 37 tests failed
Please report to bas...@li...
===================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/home/carl/bashdb-4.2-0.8/test/integration'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/carl/bashdb-4.2-0.8/test/integration'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/carl/bashdb-4.2-0.8/test'
make: *** [check-recursive] Error 1

Re: [Bashdb-devel] basdb installer issue

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

On Mon, Jul 9, 2012 at 8:06 AM, siva nagi reddy <vsn...@gm...>wrote:

> Hi ,
>
> While doing installtion of bashdb  I got below error.
>
> kddi-cm-1# ./configure
> checking for gcc... no
> checking for cc... no
> checking for cl.exe... no
> configure: error: in `/tmp/bashdb-4.2-0.8':
> configure: error: no acceptable C compiler found in $PATH
> See `config.log' for more details.
>
> could you please let me know how to procced ?
>

What does "checking for gcc .. no"  up to "no acceptable C compiler found
in $PATH" suggest to you?

bashdb doesn't strictly need a C compiler so I have changed current git
sources http://sourceforge.net/scm/?type=git&group_id=61395 not to give an
error when one isn't found.



> I am trying on solaris OS.
>
> Thanks in advance.
>
> Regards,
> Siva.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>
>

[Bashdb-devel] basdb installer issue

[siva n. r. <vsn...@gm...>]

Hi ,

While doing installtion of bashdb  I got below error.

kddi-cm-1# ./configure
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/tmp/bashdb-4.2-0.8':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

could you please let me know how to procced ?

I am trying on solaris OS.

Thanks in advance.

Regards,
Siva.

[Bashdb-devel] Fwd: Documentation on interaction with bashdb

[niXman <i.n...@gm...>]

Please tell me, commands for bashdb and other of your debuggers, are
identical? That is a front-end can work with all of your debuggers?

Regards.

2011/12/8 Rocky Bernstein <ro...@gn...>:
> On Thu, Dec 8, 2011 at 12:17 AM, niXman <i.n...@gm...> wrote:
>>
>> Hi Rocky!
>>
>> I want to write in C++/Qt front-end for bashdb.
>> Where can I get documentation on the interaction with bashdb?
>
>
> The best place to start is the documentation, the reference guide that comes
> with the distribution. You can also find it online at
> http://www.rodericksmith.plus.com/outlines/manuals/bashdbOutline.html
>
> What DDD and the emacs front-end (and I image the Eclipse front end) do is
> send commands and parse output that comes back from the debugger. This is
> not an ideal way to go, but, largely, I don't know of a better way to do
> things.
>
> To reduce unnecessary polling, a while back there was an "annotation" mode
> added to bashdb. The idea is that when rather than have the front-end query
> for information to see if something has changed, the debugger would by
> default post information when there is a change. For example when there is a
> change to the stack. To use that, there is the debugger command  "set
> annotate 1". The annotation output is prefaced by two null characters after
> a newline; after that is the kind of output, "stack" or "breakpoints". The
> older emacs front end that came with bashdb used that.
>
> I've since been rewriting this Emacs front end to support lots of debuggers,
> I don't use that anymore. But having worked a little bit on the front ends
> has made me more sensitive about  providing information that front-ends can
> use. That is why when bashdb leaves, it gives a termination message. Or why
> when you set a breakpoint a message comes back indication that the
> breakpoint was set and where it was set.
>
> Lastly I should also mention that there is --tty option to bashdb that tells
> it what tty to use for debugger input and output. The intent is to be able
> to more easily separate debugger input and output from debugged program
> input and output.
>
> Good luck and let me know when you come up with something.
>
>
>
>
>>
>>
>> Thank you.
>>
>>
>> ------------------------------------------------------------------------------
>> Cloud Services Checklist: Pricing and Packaging Optimization
>> This white paper is intended to serve as a reference, checklist and point
>> of
>> discussion for anyone considering optimizing the pricing and packaging
>> model
>> of a cloud services business. Read Now!
>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>> _______________________________________________
>> Bashdb-devel mailing list
>> Bas...@li...
>> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>
>

[Bashdb-devel] Documentation on interaction with bashdb

[niXman <i.n...@gm...>]

Hi Rocky!

I want to write in C++/Qt front-end for bashdb.
Where can I get documentation on the interaction with bashdb?

Thank you.

[Bashdb-devel] Recent bash debugger changes.

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

I am currently planning a release around March 15, the ides of March.

Changes include:

 - Updates for bash 4.2
 - 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")

Haven't done this yet, but nested debugging of expressions. Previously I
allowed only file names and
I wasn't setting variables properly there.

- - -

As I work more and more with debuggers, I slowly learn more about how to do
this better, more easily and how to
write better POSIX shell code. Each release helps me cover up
the embarrassment of code and poorly-
written code of the previous base. (There is still plenty of flaky code in
there that should be improved.)

[Bashdb-devel] 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.

Re: [Bashdb-devel] test failure when installing bashdb-4.0-0.4

[Rocky B. <roc...@gm...>]

Over time some of the line number that bashdb reports have changed and this
is probably the discrepancy I just got when I tried to run the integration
tests. I've updated git bashdb to not treat this as an error.

However to see if this is the specific problem you have, look in /tmp and
you'll probably see two files /tmp/sig-filtered.check and
/tmp/sig-filtered.right. If you do a diff on these two files the differences
might be something like:

$ ./test-sig
--- /tmp/sig-filtered.check    2010-05-27 23:08:10.020520366 +0200
+++ /tmp/sig-filtered.right    2010-05-27 23:08:10.012523050 +0200
@@ -38,7 +38,7 @@
 SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
"$BASH_COMMAND" "$@"' SIGTERM
 +continue
 Program received signal SIGTERM (15)...
-->0 in file `eval.sh' at line 1
+->0 in file `eval.sh' at line 2
 ##1 _Dbg_do_eval("kill", "-TERM", "$$") called from file `processor.sh' at
line 403
 ##2 _Dbg_onecmd("eval", "kill -TERM $$") called from file `processor.sh' at
line 168
 ##3 _Dbg_process_commands() called from file `hook.sh' at line 188
@@ -48,14 +48,14 @@
 +### Should have printed a stack trace above...
 +continue
 +where 1
-->0 in file `sig.sh' at line 1
+->0 in file `sig.sh' at line 29

and there may be other lines that are similar.

In general for reporting bugs, what is helpful is not only the version of
bashdb you are using but also of bash which you can get by bash --version.
Also the specific version of Ubuntu is helpful.

On Thu, May 27, 2010 at 5:34 PM, Elmer Fittery <elm...@an...>wrote:

> I am using Ubuntu
>
>
> FAIL: test-sig
> ===================================================
> 1 of 33 tests failed
> Please report to bas...@li...
> ===================================================
> make[3]: *** [check-TESTS] Error 1
> make[3]: Leaving directory
> `/home/elmer/downloads/bashdb-4.0-0.4/test/integration'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory
> `/home/elmer/downloads/bashdb-4.0-0.4/test/integration'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory `/home/elmer/downloads/bashdb-4.0-0.4/test'
> make: *** [check-recursive] Error 1
>
> If you would like more information, email me with what you would like.
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>

[Bashdb-devel] test failure when installing bashdb-4.0-0.4

[Elmer F. <elm...@an...>]

I am using Ubuntu


FAIL: test-sig
===================================================
1 of 33 tests failed
Please report to bas...@li...
===================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory
`/home/elmer/downloads/bashdb-4.0-0.4/test/integration'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/home/elmer/downloads/bashdb-4.0-0.4/test/integration'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/elmer/downloads/bashdb-4.0-0.4/test'
make: *** [check-recursive] Error 1

If you would like more information, email me with what you would like.

Re: [Bashdb-devel] 1 of 33 tests failed

[Rocky B. <roc...@gm...>]

That failure looks like a bug in the test routine. Probably if you copy
<bashdb-dir>/test/data/sig-Darwin.right to <bashdb-dir>/test/data/sig.right
I think that test will pass. (And even if not don't worry about the failure.


Some versions of bash == I think older ones -- don't update the line numbers
on a TERM signal properly.  It would be helpful to know what version of bash
and what patchlevel you've got so I can code this into the test.



On Wed, Mar 31, 2010 at 10:03 AM, Klaus Sandner <sa...@ks...> wrote:

> I am looking for an explanation of my error received installing bashdb
> --with-bash-src.
> I want to use the bash debugger for ddd
>
> I hope my question is not lost.
> here is the list of the output during make check
>
> with regard
>
> Klaus
>
> Making check in builtin
> make[1]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/builtin'
> make[1]: Für das Ziel »check« ist nichts zu tun.
> make[1]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/builtin'
> Making check in command
> make[1]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/command'
> make[1]: Für das Ziel »check« ist nichts zu tun.
> make[1]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/command'
> Making check in lib
> make[1]: Betrete Verzeichnis '/home/sand/make_bashdb/bashdb-4.0-0.4/lib'
> make[1]: Für das Ziel »check« ist nichts zu tun.
> make[1]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/lib'
> Making check in doc
> make[1]: Betrete Verzeichnis '/home/sand/make_bashdb/bashdb-4.0-0.4/doc'
> make[1]: Für das Ziel »check« ist nichts zu tun.
> make[1]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/doc'
> Making check in test
> make[1]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test'
> Making check in unit
> make[2]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
> make  check-TESTS
> make[3]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
> test_set0
>
> Ran 1 test.
>
> OK
> PASS: test-set0.sh
> test_alias
>
> Ran 1 test.
>
> OK
> PASS: test-alias.sh
> test_breakpoint
>
> Ran 1 test.
>
> OK
> PASS: test-break.sh
> test_preserve_set_opts
> bash Shell Debugger, release 4.0-0.4
>
> Copyright 2002, 2003, 2004, 2006, 2007, 2008, 2009 Rocky Bernstein
> This is free software, covered by the GNU General Public License, and
> you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
>
> test-bashdb-trace.sh:
> '/home/sand/make_bashdb/bashdb-4.0-0.4/dbg-opts.sh' is not a directory.
> test-bashdb-trace.sh: Perhaps bashdb is installed wrong (if its
> installed).
> test-bashdb-trace.sh: Try running bashdb using -L (with a different
> directory).
> test-bashdb-trace.sh: Run bashdb --help for a list and explanation of
> options.
>
> Ran 1 test.
>
> OK
> PASS: test-bashdb-trace.sh
> test_columnized
>
> Ran 1 test.
>
> OK
> PASS: test-columns.sh
> test_glob_filename
> test_adjust_filename
> test_resolve_expand_filename
>
> Ran 3 tests.
>
> OK
> PASS: test-file.sh
> test_copies
> test_defined
> test_esc_dq
> test_is_function
> test_traced
> test_onoff
> test_parse_linespec
> test_set_debugger_internal
> test_set_q
> test_split
>
> Ran 10 tests.
>
> OK
> PASS: test-fns.sh
> test_print_frame
> test_frame_adjust
>
> Ran 2 tests.
>
> OK
> PASS: test-frame.sh
> test_progress_show
>
> Ran 1 test.
>
> OK
> PASS: test-io.sh
> test_msg
> test_undefined
>
> Ran 2 tests.
>
> OK
> PASS: test-msg.sh
> test_expand_filename
> test_do_show_version
>
> Ran 2 tests.
>
> OK
> PASS: test-pre.sh
> test_not_running
>
> Ran 1 test.
>
> OK
> PASS: test-run.sh
> test_sort
>
> Ran 1 test.
>
> OK
> PASS: test-sort.sh
> test_save_restore_IFS_PS4
>
> Ran 1 test.
>
> OK
> PASS: test-save-restore.sh
> ===================
> All 14 tests passed
> ===================
> make[3]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
> make[2]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
> Making check in data
> make[2]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
> make  action.cmd action.right brkpt1.cmd brkpt1.right brkpt2.cmd
> brkpt2.right brkpt3.cmd brkpt3.right bug-args.cmd bug-args.right
> bug-source.cmd bug-source.right bug-step.cmd bug-step.right
> bug-step-subshell.cmd bug-step-subshell.right bugI.cmd bugI.right
> bugIFS.cmd bugIFS.right command.cmd command.right complete.cmd
> complete.right continue.cmd debug.cmd debug.right debug2.cmd display.cmd
> display.right enable.cmd enable.right finish.cmd finish.right frame.cmd
> frame.right interrupt.right list.cmd list.right lopts.right
> misc-output.right misc-output-41.right misc.cmd misc.right multi1.cmd
> multi1.right multi2.cmd multi2.right multi3.cmd multi3.right multi4.cmd
> multi4.right parm.cmd parm.right prof1.cmd prof2.cmd quit.cmd
> restart.cmd restart.right restart2.cmd search.cmd search.right
> setshow.cmd setshow.right settrace.cmd settrace.right sig.cmd sig.right
> sig-41.right sig-Darwin.right skip.cmd skip.right sopts.right
> subshell1.cmd subshell1.right subshell2.cmd subshell2.right
> subshell3.cmd subshell3.right subshell4.cmd subshell4.right tbreak.cmd
> tbreak.right trace.right trace2.right watch1.cmd watch1.right watch2.cmd
> watch2.right
> make[3]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
> make[3]: Für das Ziel »action.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »action.right« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt1.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt1.right« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt2.right« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt3.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt3.right« ist nichts zu tun.
> make[3]: Für das Ziel »bug-args.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bug-args.right« ist nichts zu tun.
> make[3]: Für das Ziel »bug-source.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bug-source.right« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step.right« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step-subshell.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step-subshell.right« ist nichts zu tun.
> make[3]: Für das Ziel »bugI.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bugI.right« ist nichts zu tun.
> make[3]: Für das Ziel »bugIFS.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »bugIFS.right« ist nichts zu tun.
> make[3]: Für das Ziel »command.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »command.right« ist nichts zu tun.
> make[3]: Für das Ziel »complete.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »complete.right« ist nichts zu tun.
> make[3]: Für das Ziel »continue.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »debug.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »debug.right« ist nichts zu tun.
> make[3]: Für das Ziel »debug2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »display.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »display.right« ist nichts zu tun.
> make[3]: Für das Ziel »enable.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »enable.right« ist nichts zu tun.
> make[3]: Für das Ziel »finish.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »finish.right« ist nichts zu tun.
> make[3]: Für das Ziel »frame.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »frame.right« ist nichts zu tun.
> make[3]: Für das Ziel »interrupt.right« ist nichts zu tun.
> make[3]: Für das Ziel »list.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »list.right« ist nichts zu tun.
> make[3]: Für das Ziel »lopts.right« ist nichts zu tun.
> make[3]: Für das Ziel »misc-output.right« ist nichts zu tun.
> make[3]: Für das Ziel »misc-output-41.right« ist nichts zu tun.
> make[3]: Für das Ziel »misc.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »misc.right« ist nichts zu tun.
> make[3]: Für das Ziel »multi1.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »multi1.right« ist nichts zu tun.
> make[3]: Für das Ziel »multi2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »multi2.right« ist nichts zu tun.
> make[3]: Für das Ziel »multi3.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »multi3.right« ist nichts zu tun.
> make[3]: Für das Ziel »multi4.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »multi4.right« ist nichts zu tun.
> make[3]: Für das Ziel »parm.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »parm.right« ist nichts zu tun.
> make[3]: Für das Ziel »prof1.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »prof2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »quit.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »restart.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »restart.right« ist nichts zu tun.
> make[3]: Für das Ziel »restart2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »search.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »search.right« ist nichts zu tun.
> make[3]: Für das Ziel »setshow.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »setshow.right« ist nichts zu tun.
> make[3]: Für das Ziel »settrace.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »settrace.right« ist nichts zu tun.
> make[3]: Für das Ziel »sig.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »sig.right« ist nichts zu tun.
> make[3]: Für das Ziel »sig-41.right« ist nichts zu tun.
> make[3]: Für das Ziel »sig-Darwin.right« ist nichts zu tun.
> make[3]: Für das Ziel »skip.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »skip.right« ist nichts zu tun.
> make[3]: Für das Ziel »sopts.right« ist nichts zu tun.
> make[3]: Für das Ziel »subshell1.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »subshell1.right« ist nichts zu tun.
> make[3]: Für das Ziel »subshell2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »subshell2.right« ist nichts zu tun.
> make[3]: Für das Ziel »subshell3.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »subshell3.right« ist nichts zu tun.
> make[3]: Für das Ziel »subshell4.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »subshell4.right« ist nichts zu tun.
> make[3]: Für das Ziel »tbreak.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »tbreak.right« ist nichts zu tun.
> make[3]: Für das Ziel »trace.right« ist nichts zu tun.
> make[3]: Für das Ziel »trace2.right« ist nichts zu tun.
> make[3]: Für das Ziel »watch1.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »watch1.right« ist nichts zu tun.
> make[3]: Für das Ziel »watch2.cmd« ist nichts zu tun.
> make[3]: Für das Ziel »watch2.right« ist nichts zu tun.
> make[3]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
> make[2]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
> Making check in example
> make[2]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
> make  bug-args.sh.in bug-step.sh bug-step-subshell.sh bugI.sh
> bugIFS.sh.in dbg-test1.sh dbg-test1.sub dbg-test2.sh debug.sh
> hanoi.sh.in interrupt.sh.in nexting.sh parm.sh restartbug.sh settrace.sh
> skip.sh subshell.sh
> make[3]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
> make[3]: Für das Ziel »bug-args.sh.in« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step.sh« ist nichts zu tun.
> make[3]: Für das Ziel »bug-step-subshell.sh« ist nichts zu tun.
> make[3]: Für das Ziel »bugI.sh« ist nichts zu tun.
> make[3]: Für das Ziel »bugIFS.sh.in« ist nichts zu tun.
> make[3]: Für das Ziel »dbg-test1.sh« ist nichts zu tun.
> make[3]: Für das Ziel »dbg-test1.sub« ist nichts zu tun.
> make[3]: Für das Ziel »dbg-test2.sh« ist nichts zu tun.
> make[3]: Für das Ziel »debug.sh« ist nichts zu tun.
> make[3]: Für das Ziel »hanoi.sh.in« ist nichts zu tun.
> make[3]: Für das Ziel »interrupt.sh.in« ist nichts zu tun.
> make[3]: Für das Ziel »nexting.sh« ist nichts zu tun.
> make[3]: Für das Ziel »parm.sh« ist nichts zu tun.
> make[3]: Für das Ziel »restartbug.sh« ist nichts zu tun.
> make[3]: Für das Ziel »settrace.sh« ist nichts zu tun.
> make[3]: Für das Ziel »skip.sh« ist nichts zu tun.
> make[3]: Für das Ziel »subshell.sh« ist nichts zu tun.
> make[3]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
> make[2]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
> Making check in integration
> make[2]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> make  brkpt1.tests brkpt2.tests brkpt3.tests check-common.sh.in
> interrupt.tests interrupt-3.tests lopts.tests multi.sh setshow.tests
> settrace.tests sig.sh sig.tests sopts.tests subshell1.tests
> subshell2.tests subshell3.tests subshell4.tests trace.tests trace2.tests
> make[3]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> make[3]: Für das Ziel »brkpt1.tests« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt2.tests« ist nichts zu tun.
> make[3]: Für das Ziel »brkpt3.tests« ist nichts zu tun.
> make[3]: Für das Ziel »check-common.sh.in« ist nichts zu tun.
> make[3]: Für das Ziel »interrupt.tests« ist nichts zu tun.
> make[3]: Für das Ziel »interrupt-3.tests« ist nichts zu tun.
> make[3]: Für das Ziel »lopts.tests« ist nichts zu tun.
> make[3]: Für das Ziel »multi.sh« ist nichts zu tun.
> make[3]: Für das Ziel »setshow.tests« ist nichts zu tun.
> make[3]: Für das Ziel »settrace.tests« ist nichts zu tun.
> make[3]: Für das Ziel »sig.sh« ist nichts zu tun.
> make[3]: Für das Ziel »sig.tests« ist nichts zu tun.
> make[3]: Für das Ziel »sopts.tests« ist nichts zu tun.
> make[3]: Für das Ziel »subshell1.tests« ist nichts zu tun.
> make[3]: Für das Ziel »subshell2.tests« ist nichts zu tun.
> make[3]: Für das Ziel »subshell3.tests« ist nichts zu tun.
> make[3]: Für das Ziel »subshell4.tests« ist nichts zu tun.
> make[3]: Für das Ziel »trace.tests« ist nichts zu tun.
> make[3]: Für das Ziel »trace2.tests« ist nichts zu tun.
> make[3]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> make  check-TESTS
> make[3]: Betrete Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> PASS: test-action
> checking brkpt1...
> checking brkpt2...
> checking brkpt3...
> PASS: test-brkpt
> PASS: test-bug-args
> PASS: test-bugI
> PASS: test-bugIFS
> PASS: test-bug-source
> PASS: test-command
> PASS: test-complete
> PASS: test-debug
> PASS: test-enable
> PASS: test-display
> PASS: test-finish
> PASS: test-frame
> --- ./interrupt.check   2010-03-31 15:39:49.142436250 +0200
> +++ /home/sand/make_bashdb/bashdb-4.0-0.4/test/data/interrupt.right
> 2009-06-26 06:52:05.000000000 +0200
> @@ -1,4 +1,3 @@
>  Program received signal SIGTERM (15)...
>  ##0 in file `interrupt.sh' at line 0
>  ##1 main() called from file `interrupt.sh' at line 0
> -
> PASS: test-interrupt
> PASS: test-list
> PASS: test-lopts
> PASS: test-misc
> PASS: test-multi
> PASS: test-parm
> PASS: test-restart
> PASS: test-search
> PASS: test-setshow
> PASS: test-settrace
> --- /tmp/sig-filtered.check     2010-03-31 15:40:11.494422400 +0200
> +++ /tmp/sig-filtered.right     2010-03-31 15:40:11.490431759 +0200
> @@ -38,7 +38,7 @@
>  SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
> "$BASH_COMMAND" "$@"' SIGTERM
>  +continue
>  Program received signal SIGTERM (15)...
> -->0 in file `eval.sh' at line 1
> +->0 in file `eval.sh' at line 2
>  ##1 _Dbg_do_eval("kill", "-TERM", "$$") called from file `processor.sh'
> at line 402
>  ##2 _Dbg_onecmd("eval", "kill -TERM $$") called from file
> `processor.sh' at line 167
>  ##3 _Dbg_process_commands() called from file `hook.sh' at line 188
> @@ -48,16 +48,15 @@
>  +### Should have printed a stack trace above...
>  +continue
>  +where 1
> -->0 in file `sig.sh' at line 1
> +->0 in file `sig.sh' at line 29
>  +continue
>  Program received signal SIGINT (2)...
> -->0 in file `sig.sh' at line 1
> +->0 in file `sig.sh' at line 23
>  ##1 source("sig.sh") called from file `bashdb' at line 157
>  ##2 main() called from file `bashdb' at line 0
>  Program received signal SIGINT (2)...
> -->0 in file `sig.sh' at line 1
> +->0 in file `sig.sh' at line 24
>  ##1 source("sig.sh") called from file `bashdb' at line 157
>  ##2 main() called from file `bashdb' at line 0
>  Debugged program terminated normally. Use q to quit or R to restart.
>  +kill
> -sig.tests: Zeile 12:  5761 Killed                  $SH
> ${top_builddir}/bashdb -B -q -L $top_builddir -x $cmdfile
> $debugged_script
> FAIL: test-sig
> PASS: test-skip
> PASS: test-sopts
> PASS: test-bug-step
> PASS: test-bug-step-subshell
> checking subshell1...
> checking subshell2...
> checking subshell3...
> PASS: test-subshell
> PASS: test-tbreak
> checking trace...
> checking trace2...
> PASS: test-trace
> PASS: test-watch1
> PASS: test-watch2
> ===================================================
> 1 of 33 tests failed
> Please report to bas...@li...
> ===================================================
> make[3]: *** [check-TESTS] Fehler 1
> make[3]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> make[2]: *** [check-am] Fehler 2
> make[2]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
> make[1]: *** [check-recursive] Fehler 1
> make[1]: Verlasse Verzeichnis
> '/home/sand/make_bashdb/bashdb-4.0-0.4/test'
> make: *** [check-recursive] Fehler 1
> sand@amilo:~/make_bashdb/bashdb-4.0-0.4$
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>

[Bashdb-devel] 1 of 33 tests failed

[Klaus S. <sa...@ks...>]

I am looking for an explanation of my error received installing bashdb
--with-bash-src. 
I want to use the bash debugger for ddd 

I hope my question is not lost.
here is the list of the output during make check

with regard 

Klaus

Making check in builtin
make[1]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/builtin'
make[1]: Für das Ziel »check« ist nichts zu tun.
make[1]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/builtin'
Making check in command
make[1]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/command'
make[1]: Für das Ziel »check« ist nichts zu tun.
make[1]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/command'
Making check in lib
make[1]: Betrete Verzeichnis '/home/sand/make_bashdb/bashdb-4.0-0.4/lib'
make[1]: Für das Ziel »check« ist nichts zu tun.
make[1]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/lib'
Making check in doc
make[1]: Betrete Verzeichnis '/home/sand/make_bashdb/bashdb-4.0-0.4/doc'
make[1]: Für das Ziel »check« ist nichts zu tun.
make[1]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/doc'
Making check in test
make[1]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test'
Making check in unit
make[2]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
make  check-TESTS
make[3]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
test_set0

Ran 1 test.

OK
PASS: test-set0.sh
test_alias

Ran 1 test.

OK
PASS: test-alias.sh
test_breakpoint

Ran 1 test.

OK
PASS: test-break.sh
test_preserve_set_opts
bash Shell Debugger, release 4.0-0.4

Copyright 2002, 2003, 2004, 2006, 2007, 2008, 2009 Rocky Bernstein
This is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.

test-bashdb-trace.sh:
'/home/sand/make_bashdb/bashdb-4.0-0.4/dbg-opts.sh' is not a directory.
test-bashdb-trace.sh: Perhaps bashdb is installed wrong (if its
installed).
test-bashdb-trace.sh: Try running bashdb using -L (with a different
directory).
test-bashdb-trace.sh: Run bashdb --help for a list and explanation of
options.

Ran 1 test.

OK
PASS: test-bashdb-trace.sh
test_columnized

Ran 1 test.

OK
PASS: test-columns.sh
test_glob_filename
test_adjust_filename
test_resolve_expand_filename

Ran 3 tests.

OK
PASS: test-file.sh
test_copies
test_defined
test_esc_dq
test_is_function
test_traced
test_onoff
test_parse_linespec
test_set_debugger_internal
test_set_q
test_split

Ran 10 tests.

OK
PASS: test-fns.sh
test_print_frame
test_frame_adjust

Ran 2 tests.

OK
PASS: test-frame.sh
test_progress_show

Ran 1 test.

OK
PASS: test-io.sh
test_msg
test_undefined

Ran 2 tests.

OK
PASS: test-msg.sh
test_expand_filename
test_do_show_version

Ran 2 tests.

OK
PASS: test-pre.sh
test_not_running

Ran 1 test.

OK
PASS: test-run.sh
test_sort

Ran 1 test.

OK
PASS: test-sort.sh
test_save_restore_IFS_PS4

Ran 1 test.

OK
PASS: test-save-restore.sh
===================
All 14 tests passed
===================
make[3]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
make[2]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/unit'
Making check in data
make[2]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
make  action.cmd action.right brkpt1.cmd brkpt1.right brkpt2.cmd
brkpt2.right brkpt3.cmd brkpt3.right bug-args.cmd bug-args.right
bug-source.cmd bug-source.right bug-step.cmd bug-step.right
bug-step-subshell.cmd bug-step-subshell.right bugI.cmd bugI.right
bugIFS.cmd bugIFS.right command.cmd command.right complete.cmd
complete.right continue.cmd debug.cmd debug.right debug2.cmd display.cmd
display.right enable.cmd enable.right finish.cmd finish.right frame.cmd
frame.right interrupt.right list.cmd list.right lopts.right
misc-output.right misc-output-41.right misc.cmd misc.right multi1.cmd
multi1.right multi2.cmd multi2.right multi3.cmd multi3.right multi4.cmd
multi4.right parm.cmd parm.right prof1.cmd prof2.cmd quit.cmd
restart.cmd restart.right restart2.cmd search.cmd search.right
setshow.cmd setshow.right settrace.cmd settrace.right sig.cmd sig.right
sig-41.right sig-Darwin.right skip.cmd skip.right sopts.right
subshell1.cmd subshell1.right subshell2.cmd subshell2.right
subshell3.cmd subshell3.right subshell4.cmd subshell4.right tbreak.cmd
tbreak.right trace.right trace2.right watch1.cmd watch1.right watch2.cmd
watch2.right
make[3]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
make[3]: Für das Ziel »action.cmd« ist nichts zu tun.
make[3]: Für das Ziel »action.right« ist nichts zu tun.
make[3]: Für das Ziel »brkpt1.cmd« ist nichts zu tun.
make[3]: Für das Ziel »brkpt1.right« ist nichts zu tun.
make[3]: Für das Ziel »brkpt2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »brkpt2.right« ist nichts zu tun.
make[3]: Für das Ziel »brkpt3.cmd« ist nichts zu tun.
make[3]: Für das Ziel »brkpt3.right« ist nichts zu tun.
make[3]: Für das Ziel »bug-args.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bug-args.right« ist nichts zu tun.
make[3]: Für das Ziel »bug-source.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bug-source.right« ist nichts zu tun.
make[3]: Für das Ziel »bug-step.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bug-step.right« ist nichts zu tun.
make[3]: Für das Ziel »bug-step-subshell.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bug-step-subshell.right« ist nichts zu tun.
make[3]: Für das Ziel »bugI.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bugI.right« ist nichts zu tun.
make[3]: Für das Ziel »bugIFS.cmd« ist nichts zu tun.
make[3]: Für das Ziel »bugIFS.right« ist nichts zu tun.
make[3]: Für das Ziel »command.cmd« ist nichts zu tun.
make[3]: Für das Ziel »command.right« ist nichts zu tun.
make[3]: Für das Ziel »complete.cmd« ist nichts zu tun.
make[3]: Für das Ziel »complete.right« ist nichts zu tun.
make[3]: Für das Ziel »continue.cmd« ist nichts zu tun.
make[3]: Für das Ziel »debug.cmd« ist nichts zu tun.
make[3]: Für das Ziel »debug.right« ist nichts zu tun.
make[3]: Für das Ziel »debug2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »display.cmd« ist nichts zu tun.
make[3]: Für das Ziel »display.right« ist nichts zu tun.
make[3]: Für das Ziel »enable.cmd« ist nichts zu tun.
make[3]: Für das Ziel »enable.right« ist nichts zu tun.
make[3]: Für das Ziel »finish.cmd« ist nichts zu tun.
make[3]: Für das Ziel »finish.right« ist nichts zu tun.
make[3]: Für das Ziel »frame.cmd« ist nichts zu tun.
make[3]: Für das Ziel »frame.right« ist nichts zu tun.
make[3]: Für das Ziel »interrupt.right« ist nichts zu tun.
make[3]: Für das Ziel »list.cmd« ist nichts zu tun.
make[3]: Für das Ziel »list.right« ist nichts zu tun.
make[3]: Für das Ziel »lopts.right« ist nichts zu tun.
make[3]: Für das Ziel »misc-output.right« ist nichts zu tun.
make[3]: Für das Ziel »misc-output-41.right« ist nichts zu tun.
make[3]: Für das Ziel »misc.cmd« ist nichts zu tun.
make[3]: Für das Ziel »misc.right« ist nichts zu tun.
make[3]: Für das Ziel »multi1.cmd« ist nichts zu tun.
make[3]: Für das Ziel »multi1.right« ist nichts zu tun.
make[3]: Für das Ziel »multi2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »multi2.right« ist nichts zu tun.
make[3]: Für das Ziel »multi3.cmd« ist nichts zu tun.
make[3]: Für das Ziel »multi3.right« ist nichts zu tun.
make[3]: Für das Ziel »multi4.cmd« ist nichts zu tun.
make[3]: Für das Ziel »multi4.right« ist nichts zu tun.
make[3]: Für das Ziel »parm.cmd« ist nichts zu tun.
make[3]: Für das Ziel »parm.right« ist nichts zu tun.
make[3]: Für das Ziel »prof1.cmd« ist nichts zu tun.
make[3]: Für das Ziel »prof2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »quit.cmd« ist nichts zu tun.
make[3]: Für das Ziel »restart.cmd« ist nichts zu tun.
make[3]: Für das Ziel »restart.right« ist nichts zu tun.
make[3]: Für das Ziel »restart2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »search.cmd« ist nichts zu tun.
make[3]: Für das Ziel »search.right« ist nichts zu tun.
make[3]: Für das Ziel »setshow.cmd« ist nichts zu tun.
make[3]: Für das Ziel »setshow.right« ist nichts zu tun.
make[3]: Für das Ziel »settrace.cmd« ist nichts zu tun.
make[3]: Für das Ziel »settrace.right« ist nichts zu tun.
make[3]: Für das Ziel »sig.cmd« ist nichts zu tun.
make[3]: Für das Ziel »sig.right« ist nichts zu tun.
make[3]: Für das Ziel »sig-41.right« ist nichts zu tun.
make[3]: Für das Ziel »sig-Darwin.right« ist nichts zu tun.
make[3]: Für das Ziel »skip.cmd« ist nichts zu tun.
make[3]: Für das Ziel »skip.right« ist nichts zu tun.
make[3]: Für das Ziel »sopts.right« ist nichts zu tun.
make[3]: Für das Ziel »subshell1.cmd« ist nichts zu tun.
make[3]: Für das Ziel »subshell1.right« ist nichts zu tun.
make[3]: Für das Ziel »subshell2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »subshell2.right« ist nichts zu tun.
make[3]: Für das Ziel »subshell3.cmd« ist nichts zu tun.
make[3]: Für das Ziel »subshell3.right« ist nichts zu tun.
make[3]: Für das Ziel »subshell4.cmd« ist nichts zu tun.
make[3]: Für das Ziel »subshell4.right« ist nichts zu tun.
make[3]: Für das Ziel »tbreak.cmd« ist nichts zu tun.
make[3]: Für das Ziel »tbreak.right« ist nichts zu tun.
make[3]: Für das Ziel »trace.right« ist nichts zu tun.
make[3]: Für das Ziel »trace2.right« ist nichts zu tun.
make[3]: Für das Ziel »watch1.cmd« ist nichts zu tun.
make[3]: Für das Ziel »watch1.right« ist nichts zu tun.
make[3]: Für das Ziel »watch2.cmd« ist nichts zu tun.
make[3]: Für das Ziel »watch2.right« ist nichts zu tun.
make[3]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
make[2]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/data'
Making check in example
make[2]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
make  bug-args.sh.in bug-step.sh bug-step-subshell.sh bugI.sh
bugIFS.sh.in dbg-test1.sh dbg-test1.sub dbg-test2.sh debug.sh
hanoi.sh.in interrupt.sh.in nexting.sh parm.sh restartbug.sh settrace.sh
skip.sh subshell.sh
make[3]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
make[3]: Für das Ziel »bug-args.sh.in« ist nichts zu tun.
make[3]: Für das Ziel »bug-step.sh« ist nichts zu tun.
make[3]: Für das Ziel »bug-step-subshell.sh« ist nichts zu tun.
make[3]: Für das Ziel »bugI.sh« ist nichts zu tun.
make[3]: Für das Ziel »bugIFS.sh.in« ist nichts zu tun.
make[3]: Für das Ziel »dbg-test1.sh« ist nichts zu tun.
make[3]: Für das Ziel »dbg-test1.sub« ist nichts zu tun.
make[3]: Für das Ziel »dbg-test2.sh« ist nichts zu tun.
make[3]: Für das Ziel »debug.sh« ist nichts zu tun.
make[3]: Für das Ziel »hanoi.sh.in« ist nichts zu tun.
make[3]: Für das Ziel »interrupt.sh.in« ist nichts zu tun.
make[3]: Für das Ziel »nexting.sh« ist nichts zu tun.
make[3]: Für das Ziel »parm.sh« ist nichts zu tun.
make[3]: Für das Ziel »restartbug.sh« ist nichts zu tun.
make[3]: Für das Ziel »settrace.sh« ist nichts zu tun.
make[3]: Für das Ziel »skip.sh« ist nichts zu tun.
make[3]: Für das Ziel »subshell.sh« ist nichts zu tun.
make[3]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
make[2]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/example'
Making check in integration
make[2]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
make  brkpt1.tests brkpt2.tests brkpt3.tests check-common.sh.in
interrupt.tests interrupt-3.tests lopts.tests multi.sh setshow.tests
settrace.tests sig.sh sig.tests sopts.tests subshell1.tests
subshell2.tests subshell3.tests subshell4.tests trace.tests trace2.tests
make[3]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
make[3]: Für das Ziel »brkpt1.tests« ist nichts zu tun.
make[3]: Für das Ziel »brkpt2.tests« ist nichts zu tun.
make[3]: Für das Ziel »brkpt3.tests« ist nichts zu tun.
make[3]: Für das Ziel »check-common.sh.in« ist nichts zu tun.
make[3]: Für das Ziel »interrupt.tests« ist nichts zu tun.
make[3]: Für das Ziel »interrupt-3.tests« ist nichts zu tun.
make[3]: Für das Ziel »lopts.tests« ist nichts zu tun.
make[3]: Für das Ziel »multi.sh« ist nichts zu tun.
make[3]: Für das Ziel »setshow.tests« ist nichts zu tun.
make[3]: Für das Ziel »settrace.tests« ist nichts zu tun.
make[3]: Für das Ziel »sig.sh« ist nichts zu tun.
make[3]: Für das Ziel »sig.tests« ist nichts zu tun.
make[3]: Für das Ziel »sopts.tests« ist nichts zu tun.
make[3]: Für das Ziel »subshell1.tests« ist nichts zu tun.
make[3]: Für das Ziel »subshell2.tests« ist nichts zu tun.
make[3]: Für das Ziel »subshell3.tests« ist nichts zu tun.
make[3]: Für das Ziel »subshell4.tests« ist nichts zu tun.
make[3]: Für das Ziel »trace.tests« ist nichts zu tun.
make[3]: Für das Ziel »trace2.tests« ist nichts zu tun.
make[3]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
make  check-TESTS
make[3]: Betrete Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
PASS: test-action
checking brkpt1...
checking brkpt2...
checking brkpt3...
PASS: test-brkpt
PASS: test-bug-args
PASS: test-bugI
PASS: test-bugIFS
PASS: test-bug-source
PASS: test-command
PASS: test-complete
PASS: test-debug
PASS: test-enable
PASS: test-display
PASS: test-finish
PASS: test-frame
--- ./interrupt.check	2010-03-31 15:39:49.142436250 +0200
+++ /home/sand/make_bashdb/bashdb-4.0-0.4/test/data/interrupt.right
2009-06-26 06:52:05.000000000 +0200
@@ -1,4 +1,3 @@
 Program received signal SIGTERM (15)...
 ##0 in file `interrupt.sh' at line 0
 ##1 main() called from file `interrupt.sh' at line 0
-
PASS: test-interrupt
PASS: test-list
PASS: test-lopts
PASS: test-misc
PASS: test-multi
PASS: test-parm
PASS: test-restart
PASS: test-search
PASS: test-setshow
PASS: test-settrace
--- /tmp/sig-filtered.check	2010-03-31 15:40:11.494422400 +0200
+++ /tmp/sig-filtered.right	2010-03-31 15:40:11.490431759 +0200
@@ -38,7 +38,7 @@
 SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
"$BASH_COMMAND" "$@"' SIGTERM
 +continue 
 Program received signal SIGTERM (15)...
-->0 in file `eval.sh' at line 1
+->0 in file `eval.sh' at line 2
 ##1 _Dbg_do_eval("kill", "-TERM", "$$") called from file `processor.sh'
at line 402
 ##2 _Dbg_onecmd("eval", "kill -TERM $$") called from file
`processor.sh' at line 167
 ##3 _Dbg_process_commands() called from file `hook.sh' at line 188
@@ -48,16 +48,15 @@
 +### Should have printed a stack trace above...
 +continue 
 +where 1
-->0 in file `sig.sh' at line 1
+->0 in file `sig.sh' at line 29
 +continue 
 Program received signal SIGINT (2)...
-->0 in file `sig.sh' at line 1
+->0 in file `sig.sh' at line 23
 ##1 source("sig.sh") called from file `bashdb' at line 157
 ##2 main() called from file `bashdb' at line 0
 Program received signal SIGINT (2)...
-->0 in file `sig.sh' at line 1
+->0 in file `sig.sh' at line 24
 ##1 source("sig.sh") called from file `bashdb' at line 157
 ##2 main() called from file `bashdb' at line 0
 Debugged program terminated normally. Use q to quit or R to restart.
 +kill 
-sig.tests: Zeile 12:  5761 Killed                  $SH
${top_builddir}/bashdb -B -q -L $top_builddir -x $cmdfile
$debugged_script
FAIL: test-sig
PASS: test-skip
PASS: test-sopts
PASS: test-bug-step
PASS: test-bug-step-subshell
checking subshell1...
checking subshell2...
checking subshell3...
PASS: test-subshell
PASS: test-tbreak
checking trace...
checking trace2...
PASS: test-trace
PASS: test-watch1
PASS: test-watch2
===================================================
1 of 33 tests failed
Please report to bas...@li...
===================================================
make[3]: *** [check-TESTS] Fehler 1
make[3]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
make[2]: *** [check-am] Fehler 2
make[2]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test/integration'
make[1]: *** [check-recursive] Fehler 1
make[1]: Verlasse Verzeichnis
'/home/sand/make_bashdb/bashdb-4.0-0.4/test'
make: *** [check-recursive] Fehler 1
sand@amilo:~/make_bashdb/bashdb-4.0-0.4$ 

[Bashdb-devel] Please try out candidate bash debugger release

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

In preparation for a release around October 27th, please try out the
candidate release tarball
http://bashdb.sourceforge.net/bashdb-4.0-0.4git.tar.bz2 or what is currently
in git right now.

>From the NEWS file for this release:

- Handle file names with embedded blanks. More parameters in calls are now
  quoted properly
- Remove the triplicate banner when running bash --debugger
- Preface more variable names with _Dbg_. Missed a use with "i" which
- Use builtin readarray if bash 4 (or greater) detected.
- Fix bug in stepping inside a subshell

Thanks

[Bashdb-devel] Possibly a release of bashdb, zshdb and kshdb Oct 27; bashdb version simplification

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

As seems to be my recent custom, I am currently planning another release of
bashdb, zshdb, and kshdb around October 27th.

For the next bashdb release I am thinking of simplifying the version
numbering scheme. In the past there was a two-level version numbering
because we wanted to support different versions of bash that might not have
had runtime-support. At this point though I think most people have bash 3.0
or greater.

So I was thinking of calling the next release 4.1 even though it will be
mostly a bug-fix release. Does this cause any problem?

[Bashdb-devel] bashdb epository has been convertied from CVS to git

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

Folks -

I have just converted the repository on sourceforge from CVS to git. So
please don't use the CVS repository more (or commit to it). No doubt there
are some rough edges on the git side, but over time I think things will
smooth out.

Thanks.

[Bashdb-devel] Release 4.0-0.4 around April 10th

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

Now that bash 4 is becoming more prevalent folks are noticing a problem that
was fixed late last November. And there was another small bug in switching
between the "next" and "step" commands.

So I'm planning a release around April 10th.

Re: [Bashdb-devel] Not able to install bashdb on freebsd 6.3

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

Version 4.0-0.2 has been out for a while, use that. It's impossible to tell
what might have gone wrong since you didn't provide any detail on any of the
failing tests.

On Tue, Jan 13, 2009 at 1:46 AM, Harish <ha...@in...> wrote:

> Hi,
>
> I am trying to use bashdb on my machine.
>
> The details of my machine is
>
> uname -a
> FreeBSD in.niksun.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16
> 04:45:45 UTC 2008     ro...@de...:/usr/obj/usr/src/sys/SMP
>  i386
>
> bash --version
> GNU bash, version 3.2.25(0)-release (i386-portbld-freebsd6.3)
> Copyright (C) 2005 Free Software Foundation, Inc.
>
> I downloaded bashdb-3.1-0.09 and performed the following steps
>
> 1. ./configure
> 2. make
> 3. make check
> 23 of 25 tests failed
> Please report to bas...@li...
>
> It failed while doing "make check", please help.
>
> Thanks
> -Harish
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>

[Bashdb-devel] Not able to install bashdb on freebsd 6.3

[Harish <ha...@in...>]

Hi,

I am trying to use bashdb on my machine.

The details of my machine is

uname -a
FreeBSD in.niksun.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008     ro...@de...:/usr/obj/usr/src/sys/SMP  i386

bash --version
GNU bash, version 3.2.25(0)-release (i386-portbld-freebsd6.3)
Copyright (C) 2005 Free Software Foundation, Inc.

I downloaded bashdb-3.1-0.09 and performed the following steps

1. ./configure
2. make
3. make check
23 of 25 tests failed
Please report to bas...@li...

It failed while doing "make check", please help.

Thanks
-Harish

[Bashdb-devel] How to use bashdb to debug a configure script

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

Recently I was tracking down why GNU autoconf configuration script
wasn't setting things the right way.

To help me, I thought I'd use bashdb and rather than call it initially
insert a call to the debugger somewhere near the portion that is
failing. That way the script runs full speed up until then. Alas,
since configure redirects input and output it took a little bit of
work to figure out how to accomplish this.

What's really needed is a command option to bashdb and bashdb-trace to
specify where to get input. I'll probably add this sometime.
Until then source'ing the tty seems to work.

First to configure I added this:

   # Somewhere near where I want to bring in the debugger....
  . /usr/local/share/bashdb/bashdb-trace
  _Dbg_debugger  # This is where

In theory this should work. But since stdin was closed calling the
debugger just caused the program to quit. So I added to
my ~/.bashdbinit this:
  source /dev/pts/5

I got /dev/pts/5 from the tty command of the shell that I was running
from. You'll have to adjust to whatever the right value is for the
time you need to run this.

Again down the line I'll probably add a --tty option (same as gdb has)
so this workaround is not needed. When this is done I image you'd get
that option in on the source command:

. /usr/local/share/bashdb/bashdb-trace --tty /dev/pts/5

[Bashdb-devel] How to use bashdb to debug a configure script

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

Recently I was tracking down why GNU autoconf configuration script
wasn't setting things the right way.

To help me, I thought I'd use bashdb and rather than call it initially
insert a call to the debugger somewhere near the portion that is
failing. That way the script runs full speed up until then. Alas,
since configure redirects input and output it took a little bit of
work to figure out how to accomplish this.

What's really needed is a command option to bashdb and bashdb-trace to
specify where to get input. I'll probably add this sometime.
Until then source'ing the tty seems to work.

First to configure I added this:

    # Somewhere near where I want to bring in the debugger....
   . /usr/local/share/bashdb/bashdb-trace
   _Dbg_debugger  # This is where

In theory this should work. But since stdin was closed calling the
debugger just caused the program to quit. So I added to
my ~/.bashdbinit this:
   source /dev/pts/5

I got /dev/pts/5 from the tty command of the shell that I was running
from. You'll have to adjust to whatever the right value is for the
time you need to run this.

Again down the line I'll probably add a --tty option (same as gdb has)
so this workaround is not needed. When this is done I image you'd get
that option in on the source command:

. /usr/local/share/bashdb/bashdb-trace --tty /dev/pts/5

Re: [Bashdb-devel] Mandriva 2009 Build error

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

This doesn't look like a serious failure.  (If you've ever run the
tests that come with bash, these messages are pretty tame compared to
those.)

But in the interest of tracking down every last detail..

The interrupt test shows a difference although the status was
"PASS". the interrupt test is a bit flaky and tricky and it works
differently on bash 4.0. As best as I can tell (and I may have this
wrong), your run has an extra or missing newline at the end of the
output.

The only failure was test-sig. And what seems to be different is the
status of various signals for SIGINT and SIGTERM ("stop" versus
"nostop" and "print" versus "noprint"). Why the difference? I'm not
sure. The routine _Dbg_init_default_traps() in lib/sig.sh called from
bashdb is supposed to set these to "stop" and "print".

I'd be curious if inside the debugger one can set these. The gdb-like
command that does this is "handle" as in "handle INT stop" and then to
see the result I think "info handle" will show the result. (Would be
nice to add command like "info handle INT" to show just how INT is
handled.)

Finally, if you are packaging this for others, especially as part of a
distribution, it might be good to compile with the readarray turned
on. Reading a large script like a configure script (typically 20K
lines line) will be slow without this builtin. Bash 4.0 will come with
this builtin (renamed to something like "maparray").

On Wed, Dec 3, 2008 at 12:46 PM, adrian hodson <no....@gm...> wrote:
>
> checking for g77... no
> checking for xlf... no
> checking for f77... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for xlf90... no
> checking for f90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for xlf95... no
> checking for f95... no
> checking for fort... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether  accepts -g... no
> checking the maximum length of command line arguments... 1572864
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... no
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> (cached) (cached) checking how to hardcode library paths into
> programs... immediate
> appending configuration tag "F77" to libtool
> checking for diff... /usr/bin/diff
> adding -w to diff in regression tests
> adding --unified to diff in regression tests
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating builtin/Makefile
> config.status: creating command/Makefile
> config.status: creating doc/Makefile
> config.status: creating lib/Makefile
> config.status: creating test/Makefile
> config.status: creating test/data/Makefile
> config.status: creating test/example/Makefile
> config.status: creating test/integration/Makefile
> config.status: creating test/unit/Makefile
> config.status: creating bashdb
> config.status: creating test/example/bugIFS.sh
> config.status: creating test/example/hanoi.sh
> config.status: creating test/example/interrupt.sh
> config.status: creating test/example/bug-args.sh
> config.status: creating test/unit/test-alias.sh
> config.status: creating test/unit/test-bashdb-trace.sh
> config.status: creating test/unit/test-break.sh
> config.status: creating test/unit/test-columns.sh
> config.status: creating test/unit/test-file.sh
> config.status: creating test/unit/test-fns.sh
> config.status: creating test/unit/test-frame.sh
> config.status: creating test/unit/test-io.sh
> config.status: creating test/unit/test-pre.sh
> config.status: creating test/unit/test-run.sh
> config.status: creating test/unit/test-save-restore.sh
> config.status: creating test/unit/test-set0.sh
> config.status: creating test/unit/test-sort.sh
> config.status: creating bashdb-main.inc
> config.status: creating bashdb-trace
> config.status: creating dbg-main.sh
> config.status: creating doc/macros.texi
> config.status: creating emacs/Makefile
> config.status: creating test/integration/check-common.sh
> config.status: creating config.h
> config.status: executing depfiles commands
> config.status: executing default commands
>
> =========================================================
> Bash version: GNU bash, version 3.2.19(2)-release (x86_64-mandriva-linux-gnu)
> Copyright (C) 2005 Free Software Foundation, Inc.
> Location: /bin/bash
> We will not try to build the builtins to speed up loading and set $0.
> We will not install GNU Emacs files.
> [adrian@localhost bashdb-4.0-0.2]$ make && make check
> make  all-recursive
> make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2'
> Making all in command
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
> Making all in lib
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
> Making all in doc
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
> texi2html ./bashdb.texi || true
> /bin/sh: texi2html: command not found
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
> Making all in test
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> Making all in unit
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> Making all in data
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> Making all in example
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> Making all in integration
> make[3]: Entering directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2'
> make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2'
> Making check in command
> make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
> make[1]: Nothing to be done for `check'.
> make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
> Making check in lib
> make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
> make[1]: Nothing to be done for `check'.
> make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
> Making check in doc
> make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
> make[1]: Nothing to be done for `check'.
> make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
> Making check in test
> make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> Making check in unit
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> make  check-TESTS
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> test_alias
>
> Ran 1 test.
>
> OK
> PASS: test-alias.sh
> test_breakpoint
>
> Ran 1 test.
>
> OK
> PASS: test-break.sh
> test_preserve_set_opts
> bash debugger, release 4.0-0.2
>
> Copyright 2002, 2003, 2004, 2006, 2007, 2008 Rocky Bernstein
> This is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
>
>
> Ran 1 test.
>
> OK
> PASS: test-bashdb-trace.sh
> test_columnized
>
> Ran 1 test.
>
> OK
> PASS: test-columns.sh
> test_glob_filename
> test_adjust_filename
> test_resolve_expand_filename
>
> Ran 3 tests.
>
> OK
> PASS: test-file.sh
> test_copies
> test_defined
> test_esc_dq
> test_is_function
> test_traced
> test_onoff
> test_parse_linespec
> test_set_debugger_internal
> test_set_q
> test_split
>
> Ran 10 tests.
>
> OK
> PASS: test-fns.sh
> test_print_frame
> test_frame_adjust
>
> Ran 2 tests.
>
> OK
> PASS: test-frame.sh
> test_msg
> test_undefined
> test_progress_show
>
> Ran 3 tests.
>
> OK
> PASS: test-io.sh
> test_expand_filename
> test_do_show_version
>
> Ran 2 tests.
>
> OK
> PASS: test-pre.sh
> test_not_running
>
> Ran 1 test.
>
> OK
> PASS: test-run.sh
> test_sort
>
> Ran 1 test.
>
> OK
> PASS: test-sort.sh
> test_save_restore_IFS_PS4
>
> Ran 1 test.
>
> OK
> PASS: test-save-restore.sh
> ===================
> All 12 tests passed
> ===================
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
> Making check in data
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> make  action.cmd action.right brkpt1.cmd brkpt1.right brkpt2.cmd
> brkpt2.right brkpt3.cmd brkpt3.right bug-args.cmd bug-args.right
> bug-source.cmd bug-source.right bugIFS.cmd bugIFS.right command.cmd
> command.right complete.cmd complete.right continue.cmd debug.cmd
> debug.right debug2.cmd display.cmd display.right finish.cmd
> finish.right frame.cmd frame.right interrupt.right list.cmd list.right
> lopts.right misc-output.right misc.cmd misc.right multi1.cmd
> multi1.right multi2.cmd multi2.right multi3.cmd multi3.right
> multi4.cmd multi4.right parm.cmd parm.right prof1.cmd prof2.cmd
> quit.cmd restart.cmd restart.right restart2.cmd search.cmd
> search.right setshow.cmd setshow.right settrace.cmd settrace.right
> sig.cmd sig.right skip.cmd skip.right sopts.right subshell1.cmd
> subshell1.right subshell2.cmd subshell2.right subshell3.cmd
> subshell3.right subshell4.cmd subshell4.right tbreak.cmd tbreak.right
> trace.right trace2.right watch1.cmd watch1.right watch2.cmd
> watch2.right
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> make[3]: Nothing to be done for `action.cmd'.
> make[3]: Nothing to be done for `action.right'.
> make[3]: Nothing to be done for `brkpt1.cmd'.
> make[3]: Nothing to be done for `brkpt1.right'.
> make[3]: Nothing to be done for `brkpt2.cmd'.
> make[3]: Nothing to be done for `brkpt2.right'.
> make[3]: Nothing to be done for `brkpt3.cmd'.
> make[3]: Nothing to be done for `brkpt3.right'.
> make[3]: Nothing to be done for `bug-args.cmd'.
> make[3]: Nothing to be done for `bug-args.right'.
> make[3]: Nothing to be done for `bug-source.cmd'.
> make[3]: Nothing to be done for `bug-source.right'.
> make[3]: Nothing to be done for `bugIFS.cmd'.
> make[3]: Nothing to be done for `bugIFS.right'.
> make[3]: Nothing to be done for `command.cmd'.
> make[3]: Nothing to be done for `command.right'.
> make[3]: Nothing to be done for `complete.cmd'.
> make[3]: Nothing to be done for `complete.right'.
> make[3]: Nothing to be done for `continue.cmd'.
> make[3]: Nothing to be done for `debug.cmd'.
> make[3]: Nothing to be done for `debug.right'.
> make[3]: Nothing to be done for `debug2.cmd'.
> make[3]: Nothing to be done for `display.cmd'.
> make[3]: Nothing to be done for `display.right'.
> make[3]: Nothing to be done for `finish.cmd'.
> make[3]: Nothing to be done for `finish.right'.
> make[3]: Nothing to be done for `frame.cmd'.
> make[3]: Nothing to be done for `frame.right'.
> make[3]: Nothing to be done for `interrupt.right'.
> make[3]: Nothing to be done for `list.cmd'.
> make[3]: Nothing to be done for `list.right'.
> make[3]: Nothing to be done for `lopts.right'.
> make[3]: Nothing to be done for `misc-output.right'.
> make[3]: Nothing to be done for `misc.cmd'.
> make[3]: Nothing to be done for `misc.right'.
> make[3]: Nothing to be done for `multi1.cmd'.
> make[3]: Nothing to be done for `multi1.right'.
> make[3]: Nothing to be done for `multi2.cmd'.
> make[3]: Nothing to be done for `multi2.right'.
> make[3]: Nothing to be done for `multi3.cmd'.
> make[3]: Nothing to be done for `multi3.right'.
> make[3]: Nothing to be done for `multi4.cmd'.
> make[3]: Nothing to be done for `multi4.right'.
> make[3]: Nothing to be done for `parm.cmd'.
> make[3]: Nothing to be done for `parm.right'.
> make[3]: Nothing to be done for `prof1.cmd'.
> make[3]: Nothing to be done for `prof2.cmd'.
> make[3]: Nothing to be done for `quit.cmd'.
> make[3]: Nothing to be done for `restart.cmd'.
> make[3]: Nothing to be done for `restart.right'.
> make[3]: Nothing to be done for `restart2.cmd'.
> make[3]: Nothing to be done for `search.cmd'.
> make[3]: Nothing to be done for `search.right'.
> make[3]: Nothing to be done for `setshow.cmd'.
> make[3]: Nothing to be done for `setshow.right'.
> make[3]: Nothing to be done for `settrace.cmd'.
> make[3]: Nothing to be done for `settrace.right'.
> make[3]: Nothing to be done for `sig.cmd'.
> make[3]: Nothing to be done for `sig.right'.
> make[3]: Nothing to be done for `skip.cmd'.
> make[3]: Nothing to be done for `skip.right'.
> make[3]: Nothing to be done for `sopts.right'.
> make[3]: Nothing to be done for `subshell1.cmd'.
> make[3]: Nothing to be done for `subshell1.right'.
> make[3]: Nothing to be done for `subshell2.cmd'.
> make[3]: Nothing to be done for `subshell2.right'.
> make[3]: Nothing to be done for `subshell3.cmd'.
> make[3]: Nothing to be done for `subshell3.right'.
> make[3]: Nothing to be done for `subshell4.cmd'.
> make[3]: Nothing to be done for `subshell4.right'.
> make[3]: Nothing to be done for `tbreak.cmd'.
> make[3]: Nothing to be done for `tbreak.right'.
> make[3]: Nothing to be done for `trace.right'.
> make[3]: Nothing to be done for `trace2.right'.
> make[3]: Nothing to be done for `watch1.cmd'.
> make[3]: Nothing to be done for `watch1.right'.
> make[3]: Nothing to be done for `watch2.cmd'.
> make[3]: Nothing to be done for `watch2.right'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
> Making check in example
> make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> make  bug-args.sh.in bugIFS.sh.in dbg-test1.sh dbg-test1.sub
> dbg-test2.sh debug.sh hanoi.sh.in interrupt.sh.in parm.sh
> restartbug.sh settrace.sh skip.sh subshell.sh
> make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> make[3]: Nothing to be done for `bug-args.sh.in'.
> make[3]: Nothing to be done for `bugIFS.sh.in'.
> make[3]: Nothing to be done for `dbg-test1.sh'.
> make[3]: Nothing to be done for `dbg-test1.sub'.
> make[3]: Nothing to be done for `dbg-test2.sh'.
> make[3]: Nothing to be done for `debug.sh'.
> make[3]: Nothing to be done for `hanoi.sh.in'.
> make[3]: Nothing to be done for `interrupt.sh.in'.
> make[3]: Nothing to be done for `parm.sh'.
> make[3]: Nothing to be done for `restartbug.sh'.
> make[3]: Nothing to be done for `settrace.sh'.
> make[3]: Nothing to be done for `skip.sh'.
> make[3]: Nothing to be done for `subshell.sh'.
> make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
> Making check in integration
> make[2]: Entering directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make  brkpt1.tests brkpt2.tests brkpt3.tests check-common.sh.in
> interrupt.tests interrupt-3.tests lopts.tests multi.sh setshow.tests
> settrace.tests sig.sh sig.tests sopts.tests subshell1.tests
> subshell2.tests subshell3.tests subshell4.tests trace.tests
> trace2.tests
> make[3]: Entering directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make[3]: Nothing to be done for `brkpt1.tests'.
> make[3]: Nothing to be done for `brkpt2.tests'.
> make[3]: Nothing to be done for `brkpt3.tests'.
> make[3]: Nothing to be done for `check-common.sh.in'.
> make[3]: Nothing to be done for `interrupt.tests'.
> make[3]: Nothing to be done for `interrupt-3.tests'.
> make[3]: Nothing to be done for `lopts.tests'.
> make[3]: Nothing to be done for `multi.sh'.
> make[3]: Nothing to be done for `setshow.tests'.
> make[3]: Nothing to be done for `settrace.tests'.
> make[3]: Nothing to be done for `sig.sh'.
> make[3]: Nothing to be done for `sig.tests'.
> make[3]: Nothing to be done for `sopts.tests'.
> make[3]: Nothing to be done for `subshell1.tests'.
> make[3]: Nothing to be done for `subshell2.tests'.
> make[3]: Nothing to be done for `subshell3.tests'.
> make[3]: Nothing to be done for `subshell4.tests'.
> make[3]: Nothing to be done for `trace.tests'.
> make[3]: Nothing to be done for `trace2.tests'.
> make[3]: Leaving directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make  check-TESTS
> make[3]: Entering directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> PASS: test-action
> checking brkpt1...
> checking brkpt2...
> checking brkpt3...
> PASS: test-brkpt
> PASS: test-bug-args
> PASS: test-bugIFS
> PASS: test-bug-source
> PASS: test-command
> PASS: test-complete
> PASS: test-debug
> PASS: test-display
> PASS: test-finish
> PASS: test-frame
> --- ./interrupt.check   2008-12-03 18:42:12.000000000 +0000
> +++ /home/adrian/Desktop/bashdb-4.0-0.2/test/data/interrupt.right       2008-10-21
> 00:06:36.000000000 +0100
> @@ -1,4 +1,3 @@
>  Program received signal SIGTERM (15)...
>  ##0 in file `interrupt.sh' at line 0
>  ##1 main() called from file `interrupt.sh' at line 0
> -
> PASS: test-interrupt
> PASS: test-list
> PASS: test-lopts
> PASS: test-misc
> PASS: test-multi
> PASS: test-parm
> PASS: test-restart
> PASS: test-search
> PASS: test-setshow
> PASS: test-settrace
> --- /tmp/sig-filtered.check     2008-12-03 18:42:36.000000000 +0000
> +++ /tmp/sig-filtered.right     2008-12-03 18:42:36.000000000 +0000
> @@ -8,6 +8,7 @@
>  EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
> "$BASH_COMMAND"' EXIT
>  EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
> "$BASH_COMMAND"' EXIT
>  SIGINT       stop   print   showstack trap -- '_Dbg_sig_handler 2
> "$BASH_COMMAND" "$@"' SIGINT
> +SIGQUIT      stop   print   showstack trap -- '_Dbg_sig_handler 3
> "$BASH_COMMAND" "$@"' SIGQUIT
>  SIGILL       stop   print   showstack trap -- '_Dbg_sig_handler 4
> "$BASH_COMMAND" "$@"' SIGILL
>  SIGTRAP      stop   print   showstack trap -- '_Dbg_sig_handler 5
> "$BASH_COMMAND" "$@"' SIGTRAP
>  SIGTERM      stop   print   showstack trap -- '_Dbg_sig_handler 15
> "$BASH_COMMAND" "$@"' SIGTERM
> @@ -31,6 +32,7 @@
>  EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
> "$BASH_COMMAND"' EXIT
>  EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
> "$BASH_COMMAND"' EXIT
>  SIGINT       nostop print   showstack trap -- '_Dbg_sig_handler 2
> "$BASH_COMMAND" "$@"' SIGINT
> +SIGQUIT      stop   print   showstack trap -- '_Dbg_sig_handler 3
> "$BASH_COMMAND" "$@"' SIGQUIT
>  SIGILL       stop   print   showstack trap -- '_Dbg_sig_handler 4
> "$BASH_COMMAND" "$@"' SIGILL
>  SIGTRAP      stop   print   showstack trap -- '_Dbg_sig_handler 5
> "$BASH_COMMAND" "$@"' SIGTRAP
>  SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
> "$BASH_COMMAND" "$@"' SIGTERM
> FAIL: test-sig
> PASS: test-skip
> PASS: test-sopts
> checking subshell1...
> checking subshell2...
> checking subshell3...
> PASS: test-subshell
> PASS: test-tbreak
> checking trace...
> checking trace2...
> PASS: test-trace
> PASS: test-watch1
> PASS: test-watch2
> ===================================================
> 1 of 29 tests failed
> Please report to bas...@li...
> ===================================================
> make[3]: *** [check-TESTS] Error 1
> make[3]: Leaving directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory
> `/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
> make: *** [check-recursive] Error 1
> [adrian@localhost bashdb-4.0-0.2]$
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel

[Bashdb-devel] Mandriva 2009 Build error

[adrian h. <no....@gm...>]

checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into
programs... immediate
appending configuration tag "F77" to libtool
checking for diff... /usr/bin/diff
adding -w to diff in regression tests
adding --unified to diff in regression tests
configure: creating ./config.status
config.status: creating Makefile
config.status: creating builtin/Makefile
config.status: creating command/Makefile
config.status: creating doc/Makefile
config.status: creating lib/Makefile
config.status: creating test/Makefile
config.status: creating test/data/Makefile
config.status: creating test/example/Makefile
config.status: creating test/integration/Makefile
config.status: creating test/unit/Makefile
config.status: creating bashdb
config.status: creating test/example/bugIFS.sh
config.status: creating test/example/hanoi.sh
config.status: creating test/example/interrupt.sh
config.status: creating test/example/bug-args.sh
config.status: creating test/unit/test-alias.sh
config.status: creating test/unit/test-bashdb-trace.sh
config.status: creating test/unit/test-break.sh
config.status: creating test/unit/test-columns.sh
config.status: creating test/unit/test-file.sh
config.status: creating test/unit/test-fns.sh
config.status: creating test/unit/test-frame.sh
config.status: creating test/unit/test-io.sh
config.status: creating test/unit/test-pre.sh
config.status: creating test/unit/test-run.sh
config.status: creating test/unit/test-save-restore.sh
config.status: creating test/unit/test-set0.sh
config.status: creating test/unit/test-sort.sh
config.status: creating bashdb-main.inc
config.status: creating bashdb-trace
config.status: creating dbg-main.sh
config.status: creating doc/macros.texi
config.status: creating emacs/Makefile
config.status: creating test/integration/check-common.sh
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing default commands

=========================================================
Bash version: GNU bash, version 3.2.19(2)-release (x86_64-mandriva-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.
Location: /bin/bash
We will not try to build the builtins to speed up loading and set $0.
We will not install GNU Emacs files.
[adrian@localhost bashdb-4.0-0.2]$ make && make check
make  all-recursive
make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2'
Making all in command
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
Making all in lib
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
Making all in doc
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
texi2html ./bashdb.texi || true
/bin/sh: texi2html: command not found
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
Making all in test
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
Making all in unit
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
Making all in data
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
Making all in example
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
Making all in integration
make[3]: Entering directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2'
make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2'
Making check in command
make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/command'
Making check in lib
make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/lib'
Making check in doc
make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/doc'
Making check in test
make[1]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
Making check in unit
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
make  check-TESTS
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
test_alias

Ran 1 test.

OK
PASS: test-alias.sh
test_breakpoint

Ran 1 test.

OK
PASS: test-break.sh
test_preserve_set_opts
bash debugger, release 4.0-0.2

Copyright 2002, 2003, 2004, 2006, 2007, 2008 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.


Ran 1 test.

OK
PASS: test-bashdb-trace.sh
test_columnized

Ran 1 test.

OK
PASS: test-columns.sh
test_glob_filename
test_adjust_filename
test_resolve_expand_filename

Ran 3 tests.

OK
PASS: test-file.sh
test_copies
test_defined
test_esc_dq
test_is_function
test_traced
test_onoff
test_parse_linespec
test_set_debugger_internal
test_set_q
test_split

Ran 10 tests.

OK
PASS: test-fns.sh
test_print_frame
test_frame_adjust

Ran 2 tests.

OK
PASS: test-frame.sh
test_msg
test_undefined
test_progress_show

Ran 3 tests.

OK
PASS: test-io.sh
test_expand_filename
test_do_show_version

Ran 2 tests.

OK
PASS: test-pre.sh
test_not_running

Ran 1 test.

OK
PASS: test-run.sh
test_sort

Ran 1 test.

OK
PASS: test-sort.sh
test_save_restore_IFS_PS4

Ran 1 test.

OK
PASS: test-save-restore.sh
===================
All 12 tests passed
===================
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/unit'
Making check in data
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
make  action.cmd action.right brkpt1.cmd brkpt1.right brkpt2.cmd
brkpt2.right brkpt3.cmd brkpt3.right bug-args.cmd bug-args.right
bug-source.cmd bug-source.right bugIFS.cmd bugIFS.right command.cmd
command.right complete.cmd complete.right continue.cmd debug.cmd
debug.right debug2.cmd display.cmd display.right finish.cmd
finish.right frame.cmd frame.right interrupt.right list.cmd list.right
lopts.right misc-output.right misc.cmd misc.right multi1.cmd
multi1.right multi2.cmd multi2.right multi3.cmd multi3.right
multi4.cmd multi4.right parm.cmd parm.right prof1.cmd prof2.cmd
quit.cmd restart.cmd restart.right restart2.cmd search.cmd
search.right setshow.cmd setshow.right settrace.cmd settrace.right
sig.cmd sig.right skip.cmd skip.right sopts.right subshell1.cmd
subshell1.right subshell2.cmd subshell2.right subshell3.cmd
subshell3.right subshell4.cmd subshell4.right tbreak.cmd tbreak.right
trace.right trace2.right watch1.cmd watch1.right watch2.cmd
watch2.right
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
make[3]: Nothing to be done for `action.cmd'.
make[3]: Nothing to be done for `action.right'.
make[3]: Nothing to be done for `brkpt1.cmd'.
make[3]: Nothing to be done for `brkpt1.right'.
make[3]: Nothing to be done for `brkpt2.cmd'.
make[3]: Nothing to be done for `brkpt2.right'.
make[3]: Nothing to be done for `brkpt3.cmd'.
make[3]: Nothing to be done for `brkpt3.right'.
make[3]: Nothing to be done for `bug-args.cmd'.
make[3]: Nothing to be done for `bug-args.right'.
make[3]: Nothing to be done for `bug-source.cmd'.
make[3]: Nothing to be done for `bug-source.right'.
make[3]: Nothing to be done for `bugIFS.cmd'.
make[3]: Nothing to be done for `bugIFS.right'.
make[3]: Nothing to be done for `command.cmd'.
make[3]: Nothing to be done for `command.right'.
make[3]: Nothing to be done for `complete.cmd'.
make[3]: Nothing to be done for `complete.right'.
make[3]: Nothing to be done for `continue.cmd'.
make[3]: Nothing to be done for `debug.cmd'.
make[3]: Nothing to be done for `debug.right'.
make[3]: Nothing to be done for `debug2.cmd'.
make[3]: Nothing to be done for `display.cmd'.
make[3]: Nothing to be done for `display.right'.
make[3]: Nothing to be done for `finish.cmd'.
make[3]: Nothing to be done for `finish.right'.
make[3]: Nothing to be done for `frame.cmd'.
make[3]: Nothing to be done for `frame.right'.
make[3]: Nothing to be done for `interrupt.right'.
make[3]: Nothing to be done for `list.cmd'.
make[3]: Nothing to be done for `list.right'.
make[3]: Nothing to be done for `lopts.right'.
make[3]: Nothing to be done for `misc-output.right'.
make[3]: Nothing to be done for `misc.cmd'.
make[3]: Nothing to be done for `misc.right'.
make[3]: Nothing to be done for `multi1.cmd'.
make[3]: Nothing to be done for `multi1.right'.
make[3]: Nothing to be done for `multi2.cmd'.
make[3]: Nothing to be done for `multi2.right'.
make[3]: Nothing to be done for `multi3.cmd'.
make[3]: Nothing to be done for `multi3.right'.
make[3]: Nothing to be done for `multi4.cmd'.
make[3]: Nothing to be done for `multi4.right'.
make[3]: Nothing to be done for `parm.cmd'.
make[3]: Nothing to be done for `parm.right'.
make[3]: Nothing to be done for `prof1.cmd'.
make[3]: Nothing to be done for `prof2.cmd'.
make[3]: Nothing to be done for `quit.cmd'.
make[3]: Nothing to be done for `restart.cmd'.
make[3]: Nothing to be done for `restart.right'.
make[3]: Nothing to be done for `restart2.cmd'.
make[3]: Nothing to be done for `search.cmd'.
make[3]: Nothing to be done for `search.right'.
make[3]: Nothing to be done for `setshow.cmd'.
make[3]: Nothing to be done for `setshow.right'.
make[3]: Nothing to be done for `settrace.cmd'.
make[3]: Nothing to be done for `settrace.right'.
make[3]: Nothing to be done for `sig.cmd'.
make[3]: Nothing to be done for `sig.right'.
make[3]: Nothing to be done for `skip.cmd'.
make[3]: Nothing to be done for `skip.right'.
make[3]: Nothing to be done for `sopts.right'.
make[3]: Nothing to be done for `subshell1.cmd'.
make[3]: Nothing to be done for `subshell1.right'.
make[3]: Nothing to be done for `subshell2.cmd'.
make[3]: Nothing to be done for `subshell2.right'.
make[3]: Nothing to be done for `subshell3.cmd'.
make[3]: Nothing to be done for `subshell3.right'.
make[3]: Nothing to be done for `subshell4.cmd'.
make[3]: Nothing to be done for `subshell4.right'.
make[3]: Nothing to be done for `tbreak.cmd'.
make[3]: Nothing to be done for `tbreak.right'.
make[3]: Nothing to be done for `trace.right'.
make[3]: Nothing to be done for `trace2.right'.
make[3]: Nothing to be done for `watch1.cmd'.
make[3]: Nothing to be done for `watch1.right'.
make[3]: Nothing to be done for `watch2.cmd'.
make[3]: Nothing to be done for `watch2.right'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/data'
Making check in example
make[2]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
make  bug-args.sh.in bugIFS.sh.in dbg-test1.sh dbg-test1.sub
dbg-test2.sh debug.sh hanoi.sh.in interrupt.sh.in parm.sh
restartbug.sh settrace.sh skip.sh subshell.sh
make[3]: Entering directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
make[3]: Nothing to be done for `bug-args.sh.in'.
make[3]: Nothing to be done for `bugIFS.sh.in'.
make[3]: Nothing to be done for `dbg-test1.sh'.
make[3]: Nothing to be done for `dbg-test1.sub'.
make[3]: Nothing to be done for `dbg-test2.sh'.
make[3]: Nothing to be done for `debug.sh'.
make[3]: Nothing to be done for `hanoi.sh.in'.
make[3]: Nothing to be done for `interrupt.sh.in'.
make[3]: Nothing to be done for `parm.sh'.
make[3]: Nothing to be done for `restartbug.sh'.
make[3]: Nothing to be done for `settrace.sh'.
make[3]: Nothing to be done for `skip.sh'.
make[3]: Nothing to be done for `subshell.sh'.
make[3]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
make[2]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test/example'
Making check in integration
make[2]: Entering directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make  brkpt1.tests brkpt2.tests brkpt3.tests check-common.sh.in
interrupt.tests interrupt-3.tests lopts.tests multi.sh setshow.tests
settrace.tests sig.sh sig.tests sopts.tests subshell1.tests
subshell2.tests subshell3.tests subshell4.tests trace.tests
trace2.tests
make[3]: Entering directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make[3]: Nothing to be done for `brkpt1.tests'.
make[3]: Nothing to be done for `brkpt2.tests'.
make[3]: Nothing to be done for `brkpt3.tests'.
make[3]: Nothing to be done for `check-common.sh.in'.
make[3]: Nothing to be done for `interrupt.tests'.
make[3]: Nothing to be done for `interrupt-3.tests'.
make[3]: Nothing to be done for `lopts.tests'.
make[3]: Nothing to be done for `multi.sh'.
make[3]: Nothing to be done for `setshow.tests'.
make[3]: Nothing to be done for `settrace.tests'.
make[3]: Nothing to be done for `sig.sh'.
make[3]: Nothing to be done for `sig.tests'.
make[3]: Nothing to be done for `sopts.tests'.
make[3]: Nothing to be done for `subshell1.tests'.
make[3]: Nothing to be done for `subshell2.tests'.
make[3]: Nothing to be done for `subshell3.tests'.
make[3]: Nothing to be done for `subshell4.tests'.
make[3]: Nothing to be done for `trace.tests'.
make[3]: Nothing to be done for `trace2.tests'.
make[3]: Leaving directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make  check-TESTS
make[3]: Entering directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
PASS: test-action
checking brkpt1...
checking brkpt2...
checking brkpt3...
PASS: test-brkpt
PASS: test-bug-args
PASS: test-bugIFS
PASS: test-bug-source
PASS: test-command
PASS: test-complete
PASS: test-debug
PASS: test-display
PASS: test-finish
PASS: test-frame
--- ./interrupt.check	2008-12-03 18:42:12.000000000 +0000
+++ /home/adrian/Desktop/bashdb-4.0-0.2/test/data/interrupt.right	2008-10-21
00:06:36.000000000 +0100
@@ -1,4 +1,3 @@
 Program received signal SIGTERM (15)...
 ##0 in file `interrupt.sh' at line 0
 ##1 main() called from file `interrupt.sh' at line 0
-
PASS: test-interrupt
PASS: test-list
PASS: test-lopts
PASS: test-misc
PASS: test-multi
PASS: test-parm
PASS: test-restart
PASS: test-search
PASS: test-setshow
PASS: test-settrace
--- /tmp/sig-filtered.check	2008-12-03 18:42:36.000000000 +0000
+++ /tmp/sig-filtered.right	2008-12-03 18:42:36.000000000 +0000
@@ -8,6 +8,7 @@
 EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
"$BASH_COMMAND"' EXIT
 EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
"$BASH_COMMAND"' EXIT
 SIGINT       stop   print   showstack trap -- '_Dbg_sig_handler 2
"$BASH_COMMAND" "$@"' SIGINT
+SIGQUIT      stop   print   showstack trap -- '_Dbg_sig_handler 3
"$BASH_COMMAND" "$@"' SIGQUIT
 SIGILL       stop   print   showstack trap -- '_Dbg_sig_handler 4
"$BASH_COMMAND" "$@"' SIGILL
 SIGTRAP      stop   print   showstack trap -- '_Dbg_sig_handler 5
"$BASH_COMMAND" "$@"' SIGTRAP
 SIGTERM      stop   print   showstack trap -- '_Dbg_sig_handler 15
"$BASH_COMMAND" "$@"' SIGTERM
@@ -31,6 +32,7 @@
 EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
"$BASH_COMMAND"' EXIT
 EXIT         stop   noprint nostack   trap -- '_Dbg_exit_handler
"$BASH_COMMAND"' EXIT
 SIGINT       nostop print   showstack trap -- '_Dbg_sig_handler 2
"$BASH_COMMAND" "$@"' SIGINT
+SIGQUIT      stop   print   showstack trap -- '_Dbg_sig_handler 3
"$BASH_COMMAND" "$@"' SIGQUIT
 SIGILL       stop   print   showstack trap -- '_Dbg_sig_handler 4
"$BASH_COMMAND" "$@"' SIGILL
 SIGTRAP      stop   print   showstack trap -- '_Dbg_sig_handler 5
"$BASH_COMMAND" "$@"' SIGTRAP
 SIGTERM      stop   noprint showstack trap -- '_Dbg_sig_handler 15
"$BASH_COMMAND" "$@"' SIGTERM
FAIL: test-sig
PASS: test-skip
PASS: test-sopts
checking subshell1...
checking subshell2...
checking subshell3...
PASS: test-subshell
PASS: test-tbreak
checking trace...
checking trace2...
PASS: test-trace
PASS: test-watch1
PASS: test-watch2
===================================================
1 of 29 tests failed
Please report to bas...@li...
===================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/home/adrian/Desktop/bashdb-4.0-0.2/test/integration'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/adrian/Desktop/bashdb-4.0-0.2/test'
make: *** [check-recursive] Error 1
[adrian@localhost bashdb-4.0-0.2]$

Re: [Bashdb-devel] set0 builtin

[Chet R. <che...@ca...>]

Masatake YAMATO wrote:

> To improve bashdb, a bash debugger, we submitted two patches to bash,
> adding readfile builtin and removing bashdb.el ever. I hope you don't
> forget it:)
> 
> We would like submit one more patch, adding set0 builtin.

I would rather see this as a loadable builtin.  mapfile had general use;
I can't see this being that general.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    ch...@ca...    http://cnswww.cns.cwru.edu/~chet/

Re: [Bashdb-devel] bashdb-4.0cvs candidate release

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

Masatake YAMATO writes:
 > When I run "make check", I got following message:
 > 
 >     --- /tmp/setshow-filtered.check	2008-10-20 11:52:25.000000000 +0900
 >     +++ /tmp/bashdb-4.0-cvs/test/data/setshow.right	2008-10-15 12:02:21.000000000 +0900
 >     @@ -308,7 +308,7 @@
 >      force: Show stepping forces a new line is off.
 >      filename: The filename in which to record the command history is
 >      save: Saving of history save is on.
 >     -size: Debugger history size is 1000
 >     +size: Debugger history size is 256

Should be fixed now and I've updated
http://bashdb.sf.net/bashdb-4.0-cvs.tar.gz with the change.

Thanks!

Re: [Bashdb-devel] bashdb-4.0cvs candidate release

[Masatake Y. <ya...@re...>]

Hi,

> In preparation for a release around October 27th, I've put a tarball
> on sourceforge which you can get at via
> http://bashdb.sf.net/bashdb-4.0-cvs.tar.gz
> 
> Please try out and let me know if there is a problem. Thanks.


When I run "make check", I got following message:

    --- /tmp/setshow-filtered.check	2008-10-20 11:52:25.000000000 +0900
    +++ /tmp/bashdb-4.0-cvs/test/data/setshow.right	2008-10-15 12:02:21.000000000 +0900
    @@ -308,7 +308,7 @@
     force: Show stepping forces a new line is off.
     filename: The filename in which to record the command history is
     save: Saving of history save is on.
    -size: Debugger history size is 1000
    +size: Debugger history size is 256
     line tracing: Show line tracing is off.
     line tracing: Show line trace delay is 0.
     listsize: Number of source lines bashdb will list by default is 10.
    FAIL: test-setshow

Masatake YAMATO