# # bashdb
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

2004/12/25 bashdb

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© December 2004 Tony Lawrence

A better debugger for your Bash scripts: http://bashdb.sourceforge.net/. Actually, it replaces Bash, so if your script was particularly strange, you might exhibit a problem when it runs under bash but not bashdb or vice versa.

That would probably be a pretty rare circumstance though.. and I can tell you that I have wanted to single-step through a shell script more than once, not because the script was broken but just because I wanted to control it more easily than messing it up with additional "read junk" lines. So maybe this is worth taking a look at it.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> bashdb

1 comment


Inexpensive and informative Apple related e-books:

Photos for Mac: A Take Control Crash Course

Are Your Bits Flipped?

Take control of Apple TV, Second Edition

Take Control of Preview

Sierra: A Take Control Crash Course





More Articles by © Tony Lawrence







Tue Apr 12 15:11:40 2005: 332   anonymous


The patched sources to bash 2.05b contain the regression tests for bash, possibly some have been improved or expanded. These all work.

Of course, whenever one *extends* a language there's a possibility that somehow there's a conflict in the extension. Names in bash (but not so in modern Korn shell) have to be global in scope so there could be a problem there too. However the name scope problem is documented - basically debugger variables start with _Dbg_. I'd find it unlikely that one of these conflicts with existing programs.

But if there ever *has* been a problem with a program running in the unpatched bash versus the debugger-enabled bash, it has never been reported as a bug or on a bashdb mailing list.

Finally, debugging support from 2.05b was put in 3.0. So aside from the name scope problem you are in fact using the same underlying bash.

------------------------


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





Get your facts first, and then you can distort them as much as you please. (Mark Twain)




Linux posts

Troubleshooting posts


This post tagged:

Misc.

Shell

UnixWords



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode