bashdb-devel

[Bashdb-devel] bashdb release for bash 3.0 ?

[Nicholas B. <nic...@ci...>]

The new released bash 3.0 lists support for the bash debugger in its change 
log, but does not ship with a copy. (even though it seems to look 
for /usr/local/lib/bashdb/bashdb-main.inc when called with --debugger) Though 
it does ship with the older example/bashdb.

Does bashdb support bash 3.0?
If so, will a standalone release of it for bash 3.0 be made?
(I can only find it in rebash2.05b)
And/Or are there plans to ship it with bash?

Though reading the post to bashdb-devel on 2003-10-23 suggests things don't 
quite work. Have these issues been resolved?

Cheers,
Nick

[Bashdb-devel] bashdb release for bash 3.0 ?

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

Nicholas Brown writes:
 > Does bashdb support bash 3.0?

I have some changes on my local disk. I'm not sure how to handle in
bashdb CVS. Depending on the consensus of other bashdb developers, it
will go there one way or another.

 > If so, will a standalone release of it for bash 3.0 be made?

Sure. I don't when though. Probably the first thing to do is get it in
public CVS. If someone else wants to lead the development for a
release, I wouldn't mind. Right now I've been working heavily on other
projects like libcdio (http://www.gnu.org/software/libcdio/ and a
debugger for GNU make http://freshmeat.net/projects/remake/)

 > Though reading the post to bashdb-devel on 2003-10-23 suggests things don't 
 > quite work. 

I guess you are referring to this from 
http://sourceforge.net/mailarchive/forum.php?thread_id=3855720&forum_id=12061 :

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

 > Have these issues been resolved?

No. But showing the last command to disambiguate where you are in a
multi-statement line is a nicety not a necessity. Alas, it's something
though that can't be fixed in the bash debugger code but has to be
done in bash 3.0.

Chet Ramey writes:

  [with respect to shipping the debugger with bash]
  > Eventually, yes, though independent development will continue.

Okay, if that's what Chet writes, I guess that's what will happen. ;-)

  > As far as I know.  Rocky is on the bash-testers list, 

Funny, I haven't been getting any bash-testers mail. Perhaps the
bash-testers list owner can check on on whether there's someone by the
name rocky subscribed. I don't recall getting any bash-testers
e-mail. The alpha announcement was forwarded to me. 

  > and I didn't hear anything back from him regarding any of the alpha or beta releases.

There is a communication problem somewhere. I thought communicated the
problem I encountered in alpha described above. I thought it weird but
not uncommon for bash not to get word back on it. Also, I don't recall
receiving a beta release announcement or a bash 3.0 announcement.

Is there a public bash-testers mailing list archive somewhere?

Re: [Bashdb-devel] bashdb release for bash 3.0 ?

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

> I guess you are referring to this from 
> http://sourceforge.net/mailarchive/forum.php?thread_id=3855720&forum_id=12061 :
> 
>    So of course, I rely on the regression tests, and although most of
>    these work in bash 3.0 not all do, notably those which fail show
>    what the upcoming command to be executed is which is used when there
>    are multiple statements on a line.  (I wrote Chet Ramey on this but
>    haven"t received any comment.)

I'll have to look back; I can't recall this immediately.

>   [with respect to shipping the debugger with bash]
>   > Eventually, yes, though independent development will continue.
> 
> Okay, if that's what Chet writes, I guess that's what will happen. ;-)

I envision the two of us getting together and putting together a bashdb
release to be included each time I make a bash release, but the two projects
proceeding at their own rates.

>   > As far as I know.  Rocky is on the bash-testers list, 
> 
> Funny, I haven't been getting any bash-testers mail.

I'll make sure you're on it.  Now that 3.0 is out, I'm interested in your
comments.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
						Live...Laugh...Love
Chet Ramey, ITS, CWRU    ch...@po...    http://tiswww.tis.cwru.edu/~chet/

Re: [Bashdb-devel] bashdb release for bash 3.0 ?

[Nicholas B. <nic...@ci...>]

Exellcent. I'm prepared to help were possible (testing etc).
I look forward to a bash 3.01 release with bashdb included. ;-)

Thanks guys for working to provide bash with script debugging support.
Cheers,
Nick

On Tuesday 17 Aug 2004 13:38, Chet Ramey wrote:
> > I guess you are referring to this from
> > http://sourceforge.net/mailarchive/forum.php?thread_id=3855720&forum_id=1
> >2061 :
> >
> >    So of course, I rely on the regression tests, and although most of
> >    these work in bash 3.0 not all do, notably those which fail show
> >    what the upcoming command to be executed is which is used when there
> >    are multiple statements on a line.  (I wrote Chet Ramey on this but
> >    haven"t received any comment.)
>
> I'll have to look back; I can't recall this immediately.
>
> >   [with respect to shipping the debugger with bash]
> >
> >   > Eventually, yes, though independent development will continue.
> >
> > Okay, if that's what Chet writes, I guess that's what will happen. ;-)
>
> I envision the two of us getting together and putting together a bashdb
> release to be included each time I make a bash release, but the two
> projects proceeding at their own rates.
>
> >   > As far as I know.  Rocky is on the bash-testers list,
> >
> > Funny, I haven't been getting any bash-testers mail.
>
> I'll make sure you're on it.  Now that 3.0 is out, I'm interested in your
> comments.
>
> Chet