Re: How to debug shell cmds?

[Dusan Juhas]

On Wed, 29 Jan 2003, Jens Schweikhardt wrote:

> Untested, and it does involve Makefile changes, but as we say in Germany,
> you can't ask for "Wash my fur but don't get me wet" :-)

Sounds crazy. Could you give me the original sentence? ;-)

>
> - Change all occurences of mkdir to $(MKDIR), which is good Makefile
>   engineering anyway. Then on the commandline:
> - If debugging: make MKDIR='echo mkdir breakpoint reached; read dummy; mkdir'
>   else          make MKDIR=mkdir
> - Hit Enter at each breakpoint to continue.

Not bad, but insufficient.
I have to deal with complicated package that contains a zillion of files
and hundreds of nested makefiles. I used mkdir but I can also be
my-$(var1)-$(var2). If it is my-huge-cmd I'd like to stop. If it is
my-stupid-cmd I don't want to care about it.
Anyway, with MKDIR it is a good start.

By the way how to stop determine that any shell command was invoked?

--
Best regards,
Dusan Juhas