Eric,
Cool, I had used bashdb before, didn't know it could trace..
Anyways, thanks, I'll try it out.
Ed
On 8/24/10 6:12 AM, "Eric Blake" wrote:
On 08/23/2010 08:27 PM, Edward Peschko wrote:
> All,
>
> I've been working lately at upgrading my debugging tools and procedures, and
> have come t
On Tue, Aug 24, 2010 at 2:44 AM, Joachim Schmitz
wrote:
> Edward Peschko wrote:
>>
>> All,
>>
>> I've been working lately at upgrading my debugging tools and
>> procedures, and have come to looking how I can improve debugging
>> bash.
>> I know about bash -x , but its terribly annoying because, ev
On 08/23/2010 08:27 PM, Edward Peschko wrote:
All,
I've been working lately at upgrading my debugging tools and procedures, and
have come to looking how I can improve debugging bash.
Have you tried the bashdb package? It takes full advantage of a wide
variety of bash features to make it pos
Edward Peschko wrote:
All,
I've been working lately at upgrading my debugging tools and
procedures, and have come to looking how I can improve debugging
bash.
I know about bash -x , but its terribly annoying because, even though
it shows the evaluated text, there is no explicit way to tie th
