Date: Wed, 8 Aug 2001 18:08:45 -0400 From: parv <parv@worldnet.att.net> To: Drew Tomlinson <drewt@writeme.com> Cc: "FreeBSD Questions (E-mail)" <freebsd-questions@FreeBSD.org> Subject: Re: How To Debug Scripts? Message-ID: <20010808180844.A78540@moo.holy.cow> In-Reply-To: <5CD46247635BD511B6B100A0CC3F023925A052@ldcmsx01.lc.ca.gov>; from drewt@writeme.com on Wed, Aug 08, 2001 at 02:55:34PM -0700 References: <5CD46247635BD511B6B100A0CC3F023925A052@ldcmsx01.lc.ca.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
this was, on the fateful occasion around Aug 08 17:55 -0400, sent by Drew Tomlinson > ... > Anyway, I have written many scripts using OpenVMS on VAXs and > Alphas. In that OS, there's a command called "set verify" that prints each > line of the script as it executes. This way I can see what symbol > substitution has taken place and exactly at what line the error(s) occurred. > Is there something similar to this for Unix scripts? after #!/bin/sh, try "set -o xtrace" & man sh(1)... -- so, do you like word games or scrabble? - parv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010808180844.A78540>