Get APLawrence.com by RSSbashdb
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 this page was useful to you, please click to help others find it:
Your +1's can help friends, contacts, and others on the web find the best stuff when they search.
Inexpensive and informative Apple related e-books:
Take Control of iPhone and iPod touch Networking &Security, iOS 4 Edition
What's New in Word 2004: Advanced
VMware Fusion 2
Apple Mail in Snow Leopard
Getting Started with DEVONthink 2
More Articles by Tony Lawrence - Find me on Google+
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
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. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Tue Apr 12 15:11:40 2005: 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.
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar