bashdb-help — A members-only discussion list for help withbashdb, remake, or pydb

Re: [Bashdb-help] bashdb 4.3-0.9: `shopt -s nullglob` results in hung process

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

Should be fixed in commit a9e7dcb. shopt nullglob saved and restored as
suggested.

On Mon, Nov 3, 2014 at 3:26 AM, John Purnell <joh...@gm...> wrote:

> If the script to be debugged has set `shopt -s  nullglob` before
> `bashdb-trace` is sourced, then bashdb either hangs at the line it is
> invoked with `_Dbg_debugger` or at the debugger quit/restart prompt if
> not. Perhaps the script's shell options could be saved and restored
> with:
>
> old_shopt=$(shopt -p)
>
> and:
>
> eval "$old_shopt" 2> /dev/null
>
> so that the debugger isn't affected by what the script's shell options
> are.
>
> Cheers
> John
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>

Re: [Bashdb-help] bashdb 4.3-0.9: test failure

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

Should be fixed in commit 086885c.

There always had been a special file to use on Darwin, but it hadn't been
used. It also needed updating.

On Mon, Nov 3, 2014 at 3:00 AM, John Purnell <joh...@gm...> wrote:

> With the following system I am getting 1 test suite failure:
>
> $ uname -v
> Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014;
> root:xnu-2422.115.4~1/RELEASE_X86_64
>
> $ gcc --version
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 6.0 (clang-600.0.47) (based on LLVM 3.5svn)
> Target: x86_64-apple-darwin13.4.0
> Thread model: posix
>
> $ bash --version
> GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin13.4.0)
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
>
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> $ bashdb --version
> bashdb, release 4.3-0.9
>
> $ cat ./bashdb-4.3-0.9-test-suite.log
> =====================================================
>     bashdb 4.3-0.9: test/integration/test-suite.log
> =====================================================
>
> # TOTAL: 40
> # PASS:  35
> # SKIP:  4
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: test-file-with-spaces
> ===========================
>
> Skipping test due to autoconf problems
>
> SKIP: test-interrupt
> ====================
>
>
> FAIL: test-sig
> ==============
>
> bash(43327,0x7fff750a6310) malloc: *** error for object 0x4000000000000:
> pointer being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> /Users/jp/Downloads/bashdb-4.3-0.9/test/integration/check-common.sh:
> line 25: 43327 Abort trap: 6           $SH -- ${top_builddir}/bashdb
> $dbg_opts -x "$cmdfile" "$debugged_script" $ARGS
> --- /tmp/sig-filtered.check     2014-10-28 08:54:25.000000000 +0200
> +++ /tmp/sig-filtered.right     2014-10-28 08:54:25.000000000 +0200
> @@ -55,3 +55,5 @@
>   +continue
>   $? is 0
>   $? is 0
> +Debugged program terminated normally. Use q to quit or R to restart.
> ++### Should have printed a stack trace above...
>
> SKIP: test-file-with-spaces
> ===========================
>
> Skipping test due to autoconf problems
>
> SKIP: test-interrupt
> ====================
>
> It doesn't seem to be affecting anything in my usage so far. Let me know
> if there is anything I can help with in resolving this if you deem it
> necessary.
>
> Cheers
> John
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>

[Bashdb-help] bashdb 4.3-0.9: `shopt -s nullglob` results in hung process

[John P. <joh...@gm...>]

If the script to be debugged has set `shopt -s  nullglob` before 
`bashdb-trace` is sourced, then bashdb either hangs at the line it is 
invoked with `_Dbg_debugger` or at the debugger quit/restart prompt if 
not. Perhaps the script's shell options could be saved and restored 
with:

old_shopt=$(shopt -p)

and:

eval "$old_shopt" 2> /dev/null

so that the debugger isn't affected by what the script's shell options 
are.

Cheers
John

[Bashdb-help] bashdb 4.3-0.9: test failure

[John P. <joh...@gm...>]

With the following system I am getting 1 test suite failure:

$ uname -v
Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; 
root:xnu-2422.115.4~1/RELEASE_X86_64

$ gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.47) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

$ bash --version
GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin13.4.0)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ bashdb --version
bashdb, release 4.3-0.9

$ cat ./bashdb-4.3-0.9-test-suite.log
=====================================================
    bashdb 4.3-0.9: test/integration/test-suite.log
=====================================================

# TOTAL: 40
# PASS:  35
# SKIP:  4
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: test-file-with-spaces
===========================

Skipping test due to autoconf problems

SKIP: test-interrupt
====================


FAIL: test-sig
==============

bash(43327,0x7fff750a6310) malloc: *** error for object 0x4000000000000: 
pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
/Users/jp/Downloads/bashdb-4.3-0.9/test/integration/check-common.sh: 
line 25: 43327 Abort trap: 6           $SH -- ${top_builddir}/bashdb 
$dbg_opts -x "$cmdfile" "$debugged_script" $ARGS
--- /tmp/sig-filtered.check	2014-10-28 08:54:25.000000000 +0200
+++ /tmp/sig-filtered.right	2014-10-28 08:54:25.000000000 +0200
@@ -55,3 +55,5 @@
  +continue
  $? is 0
  $? is 0
+Debugged program terminated normally. Use q to quit or R to restart.
++### Should have printed a stack trace above...

SKIP: test-file-with-spaces
===========================

Skipping test due to autoconf problems

SKIP: test-interrupt
====================

It doesn't seem to be affecting anything in my usage so far. Let me know 
if there is anything I can help with in resolving this if you deem it 
necessary.

Cheers
John

Re: [Bashdb-help] bashdb-4.2-0.8 make errors under Mac OS X 10.6.8

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

I seem to recall that OSX uses this dynaloader thing for creating shared
libraries. See the last paragraph of the checked answer in

http://stackoverflow.com/questions/2339679/what-are-the-differences-between-so-and-dylib-on-osx

I don't have access to a computer runnng OSX to use to try to reproduce or
work up a solution. If you do work up a solution, consider sending a patch
or posting the solution here.

Finally, I should note that you don't have to compile with source to get
the large file speedup. That code is now was incorporated into bash 4.1 (and
persists in 4.2).  What compiling with the source will however do is allow
you and bashdb to change $0. In debugging at the outset via bashdb, usually
programmers would prefer $0 to refer to the program getting debugged instead
of bashdb.

On Fri, Sep 30, 2011 at 10:42 PM, John Purnell <joh...@gm...>wrote:

> bash --version
> GNU bash, version 4.2.10(1)-release (i386-apple-darwin10.8.0)
>
> When configuring bashbd with:
>
> ./configure --with-bash=/usr/local/bin/bash \
> --with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
> --with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc \
> && make && make check
>
> all is fine. But as soon as I use:
>
> ./configure --with-bash=/usr/local/bin/bash \
> --with-bash-src=/Downloads/src/bash-4.2.10 \
> --with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
> --with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc
>
> to get large input file support make fails with the following:
>
> Making all in builtin
> gcc -DHAVE_CONFIG_H -I. -I..    -I /Downloads/src/bash-4.2.10 -I
> /Downloads/src/bash-4.2.10/include
> -I/Downloads/src/bash-4.2.10/builtins  -g -O2 -MT set0-set0.o -MD -MP
> -MF .deps/set0-set0.Tpo -c -o set0-set0.o `test -f 'set0.c' || echo
> './'`set0.c
> mv -f .deps/set0-set0.Tpo .deps/set0-set0.Po
> gcc  -g -O2   -o set0 \
>            -shared set0-set0.o
> Undefined symbols:
>  "_dollar_vars", referenced from:
>      _set0_builtin in set0-set0.o
>  "_builtin_usage", referenced from:
>      _set0_builtin in set0-set0.o
>  "_builtin_error", referenced from:
>      _set0_builtin in set0-set0.o
>  "_xmalloc", referenced from:
>      _set0_builtin in set0-set0.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [set0] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> I see from a Google search that Rocky reported the same issue on
> 2011-05-18 when building to use the builtin under cygwin. Any ideas
> for a solution.
>
> Thanks
> John
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>

[Bashdb-help] bashdb-4.2-0.8 make errors under Mac OS X 10.6.8

[John P. <joh...@gm...>]

bash --version
GNU bash, version 4.2.10(1)-release (i386-apple-darwin10.8.0)

When configuring bashbd with:

./configure --with-bash=/usr/local/bin/bash \
--with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
--with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc \
&& make && make check

all is fine. But as soon as I use:

./configure --with-bash=/usr/local/bin/bash \
--with-bash-src=/Downloads/src/bash-4.2.10 \
--with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
--with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc

to get large input file support make fails with the following:

Making all in builtin
gcc -DHAVE_CONFIG_H -I. -I..    -I /Downloads/src/bash-4.2.10 -I
/Downloads/src/bash-4.2.10/include
-I/Downloads/src/bash-4.2.10/builtins  -g -O2 -MT set0-set0.o -MD -MP
-MF .deps/set0-set0.Tpo -c -o set0-set0.o `test -f 'set0.c' || echo
'./'`set0.c
mv -f .deps/set0-set0.Tpo .deps/set0-set0.Po
gcc  -g -O2   -o set0 \
	    -shared set0-set0.o
Undefined symbols:
  "_dollar_vars", referenced from:
      _set0_builtin in set0-set0.o
  "_builtin_usage", referenced from:
      _set0_builtin in set0-set0.o
  "_builtin_error", referenced from:
      _set0_builtin in set0-set0.o
  "_xmalloc", referenced from:
      _set0_builtin in set0-set0.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [set0] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I see from a Google search that Rocky reported the same issue on
2011-05-18 when building to use the builtin under cygwin. Any ideas
for a solution.

Thanks
John

[Bashdb-help] $0

[Eric J. V. d. V. <eri...@gm...>]

Hello,

I always invoke bashdb like this,

> bashdb script.bash

But then $0  is bashdb, and not script.bash .

How can I repair this?

Thanks,

Eric J.

Re: [Bashdb-help] bashdb syntax error with for loop

[Rob W. <rcw...@gm...>]

Hi Rocky,

That's great news!

I've seen comments about complications with building bashdb correctly so
I'll be a little explicit in what I tested:

I cloned the git repo.  Then ran ./autogen.sh and make.

Then used "./bashdb -L . /tmp/bashdb_test.sh" to debug my script from within
the top-level of my git clone.

The testcase I provided passed without any problems.  Originally the problem
I saw used: "for i in $foo" with foo="/path" so I tested that too.  That
worked perfectly as well.

Thanks,
Rob

On Thu, Oct 22, 2009 at 11:24 PM, Rocky Bernstein <roc...@gm...
> wrote:

> Ok. I think I have found and fixed the problem. Thanks for whittling it
> down to something manageable.
>
> (It was something really silly; surprising it wasn't detected earlier.)
> Please try out what's in git on sourceforge or the candidate release tarball
> http://bashdb.sourceforge.net/bashdb-4.0-0.4git.tar.bz2
>
> There will probably be a general release soon.
>
> Thanks
>
>
> On Thu, Oct 22, 2009 at 3:36 PM, Rocky Bernstein <
> roc...@gm...> wrote:
>
>> Simple attempts to isolate the problem elude me so further research is
>> needed.
>>
>> However I note if the debugger is installed and bash knows about it (i.e.
>> has been compiled the right way) then this seems to work even though the
>> banner comes out multiple times:
>>
>> $/bin/bash --debugger /tmp/bashdbbug.sh
>>  Shell Debugger, release
>>
>> 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.
>>
>> Bourne-Again Shell Debugger, release
>>
>> 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.
>>
>>  Shell Debugger, release
>>
>> 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.
>>
>> (/tmp/bashdbbug.sh:3):
>> 3:    for i in /bin /etc; do
>> bashdb<0> c
>> /bin
>> /etc
>>
>> On Thu, Oct 22, 2009 at 2:40 PM, Rob Woolley <rcw...@gm...> wrote:
>>
>>> I tried using bashdb for the first time.  I was impressed with how well
>>> it was working on a 32000 line ./configure script.
>>>
>>> It had some trouble on line 23000 with a for loop.  I created a simple
>>> testcase that causes the problem to appear:
>>>
>>> #!/bin/bash
>>>
>>> for i in /bin /etc; do
>>>     echo $i
>>> done
>>>
>>> The script executes successfully without the debugger, but when the
>>> debugger is used it gives the following output:
>>>
>>> $ bashdb bashdb_test.sh
>>> bash debugger, release 4.0-0.3
>>>
>>> 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.
>>>
>>> (/tmp/bashdb_test.sh:3):
>>> 3:    for i in /bin /etc; do
>>> bashdb<0> c
>>> bashdb_test.sh: line 3: /bin: syntax error: operand expected (error token
>>> is "/bin")
>>> Debugged program terminated with code 1. Use q to quit or R to restart.
>>> bashdb<1>
>>>
>>> I'm using bashdb, release 4.0-0.3 on Fedora 11
>>>
>>> I'm happy to assist with the debugging if there's anything I can help
>>> with.
>>>
>>> Cheers,
>>> Rob
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Bashdb-help mailing list
>>> Bas...@li...
>>> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>>>
>>>
>>
>

Re: [Bashdb-help] bashdb syntax error with for loop

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

Ok. I think I have found and fixed the problem. Thanks for whittling it down
to something manageable.

(It was something really silly; surprising it wasn't detected earlier.)
Please try out what's in git on sourceforge or the candidate release tarball
http://bashdb.sourceforge.net/bashdb-4.0-0.4git.tar.bz2

There will probably be a general release soon.

Thanks

On Thu, Oct 22, 2009 at 3:36 PM, Rocky Bernstein
<roc...@gm...>wrote:

> Simple attempts to isolate the problem elude me so further research is
> needed.
>
> However I note if the debugger is installed and bash knows about it (i.e.
> has been compiled the right way) then this seems to work even though the
> banner comes out multiple times:
>
> $/bin/bash --debugger /tmp/bashdbbug.sh
>  Shell Debugger, release
>
> 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.
>
> Bourne-Again Shell Debugger, release
>
> 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.
>
>  Shell Debugger, release
>
> 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.
>
> (/tmp/bashdbbug.sh:3):
> 3:    for i in /bin /etc; do
> bashdb<0> c
> /bin
> /etc
>
> On Thu, Oct 22, 2009 at 2:40 PM, Rob Woolley <rcw...@gm...> wrote:
>
>> I tried using bashdb for the first time.  I was impressed with how well it
>> was working on a 32000 line ./configure script.
>>
>> It had some trouble on line 23000 with a for loop.  I created a simple
>> testcase that causes the problem to appear:
>>
>> #!/bin/bash
>>
>> for i in /bin /etc; do
>>     echo $i
>> done
>>
>> The script executes successfully without the debugger, but when the
>> debugger is used it gives the following output:
>>
>> $ bashdb bashdb_test.sh
>> bash debugger, release 4.0-0.3
>>
>> 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.
>>
>> (/tmp/bashdb_test.sh:3):
>> 3:    for i in /bin /etc; do
>> bashdb<0> c
>> bashdb_test.sh: line 3: /bin: syntax error: operand expected (error token
>> is "/bin")
>> Debugged program terminated with code 1. Use q to quit or R to restart.
>> bashdb<1>
>>
>> I'm using bashdb, release 4.0-0.3 on Fedora 11
>>
>> I'm happy to assist with the debugging if there's anything I can help
>> with.
>>
>> Cheers,
>> Rob
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Bashdb-help mailing list
>> Bas...@li...
>> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>>
>>
>

Re: [Bashdb-help] bashdb syntax error with for loop

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

Simple attempts to isolate the problem elude me so further research is
needed.

However I note if the debugger is installed and bash knows about it (i.e.
has been compiled the right way) then this seems to work even though the
banner comes out multiple times:

$/bin/bash --debugger /tmp/bashdbbug.sh
 Shell Debugger, release

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.

Bourne-Again Shell Debugger, release

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.

 Shell Debugger, release

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.

(/tmp/bashdbbug.sh:3):
3:    for i in /bin /etc; do
bashdb<0> c
/bin
/etc

On Thu, Oct 22, 2009 at 2:40 PM, Rob Woolley <rcw...@gm...> wrote:

> I tried using bashdb for the first time.  I was impressed with how well it
> was working on a 32000 line ./configure script.
>
> It had some trouble on line 23000 with a for loop.  I created a simple
> testcase that causes the problem to appear:
>
> #!/bin/bash
>
> for i in /bin /etc; do
>     echo $i
> done
>
> The script executes successfully without the debugger, but when the
> debugger is used it gives the following output:
>
> $ bashdb bashdb_test.sh
> bash debugger, release 4.0-0.3
>
> 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.
>
> (/tmp/bashdb_test.sh:3):
> 3:    for i in /bin /etc; do
> bashdb<0> c
> bashdb_test.sh: line 3: /bin: syntax error: operand expected (error token
> is "/bin")
> Debugged program terminated with code 1. Use q to quit or R to restart.
> bashdb<1>
>
> I'm using bashdb, release 4.0-0.3 on Fedora 11
>
> I'm happy to assist with the debugging if there's anything I can help with.
>
> Cheers,
> Rob
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>
>

[Bashdb-help] bashdb syntax error with for loop

[Rob W. <rcw...@gm...>]

I tried using bashdb for the first time.  I was impressed with how well it
was working on a 32000 line ./configure script.

It had some trouble on line 23000 with a for loop.  I created a simple
testcase that causes the problem to appear:

#!/bin/bash

for i in /bin /etc; do
    echo $i
done

The script executes successfully without the debugger, but when the debugger
is used it gives the following output:

$ bashdb bashdb_test.sh
bash debugger, release 4.0-0.3

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.

(/tmp/bashdb_test.sh:3):
3:    for i in /bin /etc; do
bashdb<0> c
bashdb_test.sh: line 3: /bin: syntax error: operand expected (error token is
"/bin")
Debugged program terminated with code 1. Use q to quit or R to restart.
bashdb<1>

I'm using bashdb, release 4.0-0.3 on Fedora 11

I'm happy to assist with the debugging if there's anything I can help with.

Cheers,
Rob

Re: [Bashdb-help] how to get bash script with bashdb?

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

Please reread Section 2.1 Starting the BASH debugger of the bashdb
manual  http://bashdb.sourceforge.net/bashdb.html#SEC7, especially the
paragraph that begins:
   There are two or three disadvantages ...

The basic problem is that bash and other POSIX shells don't allow $0
to get set. The next release of bashdb will include a built-in
function to get around this, however in order to use this, bashdb has
to be built for this which requires having the bash source around. And
building against a specific release of bash ties bashdb to it. Many
distributions that package bash don't do this (e.g. Debian) although
some do (e.g. cygwin).

On Mon, Jul 21, 2008 at 10:48 PM, Peng Yu <pen...@gm...> wrote:
> Hi,
>
> Without using bashdb, I could use "$0" to get the bash script name.
> With bashdb I don't see a way to get the script name. Can I somebody
> let me know how to do it?
>
> Thanks,
> Peng
>
>
> $ cat echo.sh
> #!/bin/bash
>
> echo $0 $1
>
>
> $ bashdb echo.sh
> Bourne-Again Shell Debugger, release bash-3.1-0.06
> Copyright 2002, 2003, 2004, 2006 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.
>
> (/tmp/echo.sh:3):
> 3:      echo $0 $1
> bashdb<0> n
> /usr/bin/bashdb
> (/usr/bin/bashdb:285):
> 285:
> bashdb<1> n
> Debugged program terminated normally. Use q to quit or R to restart.
> bashdb<2> q
>
> -------------------------------------------------------------------------
> 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-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>

[Bashdb-help] how to get bash script with bashdb?

[Peng Y. <pen...@gm...>]

Hi,

Without using bashdb, I could use "$0" to get the bash script name.
With bashdb I don't see a way to get the script name. Can I somebody
let me know how to do it?

Thanks,
Peng


$ cat echo.sh
#!/bin/bash

echo $0 $1


$ bashdb echo.sh
Bourne-Again Shell Debugger, release bash-3.1-0.06
Copyright 2002, 2003, 2004, 2006 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.

(/tmp/echo.sh:3):
3:      echo $0 $1
bashdb<0> n
/usr/bin/bashdb
(/usr/bin/bashdb:285):
285:
bashdb<1> n
Debugged program terminated normally. Use q to quit or R to restart.
bashdb<2> q