Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site burl.UUCP
Path: utzoo!watmath!clyde!burl!rcj
From: rcj@burl.UUCP (Curtis Jackson)
Newsgroups: net.unix
Subject: Re: undocumented sdb switch
Message-ID: <1142@burl.UUCP>
Date: Thu, 20-Mar-86 13:02:24 EST
Article-I.D.: burl.1142
Posted: Thu Mar 20 13:02:24 1986
Date-Received: Fri, 21-Mar-86 06:29:32 EST
References: <196@rexago1.UUCP>
Reply-To: rcj@burl.UUCP (Curtis Jackson)
Distribution: net
Organization: AT&T Technologies, Burlington NC
Lines: 28
Keywords: sdb -d path source
Summary: 

In article <196@rexago1.UUCP> rich@rexago1.UUCP (K. Richard Magill) writes:
>I found what looks like an undocumentted sdb option on a 3b2/300
>running SYSV.2.2.  It appears as though
>
>	sdb -d path
>
>will hunt through path for your source files.  This is a big help
>if you are debugging a library or two.

Have you looked at the man page?  My SVR2 User's Reference Manual (Vax)
says that the SYNOPSIS is:

sdb [ -w ] [ -W ] [ objfil [ corfil [ directory-list ] ] ]

Since I name my sdb'able version of every executable as the normal name
of the executable preceded by a 'd', and I have common code in a directory
called "asgc" on the same level as all my other code directories, I have
a function called "sd" that looks something like:

sdb d$1 - ".:../asgc"

You may be right about the -d switch; but why use something undocumented
when there is a [convenient] documented way to do the same thing?
-- 

The MAD Programmer -- 919-228-3313 (Cornet 291)
alias: Curtis Jackson	...![ ihnp4 ulysses cbosgd allegra ]!burl!rcj
			...![ ihnp4 cbosgd decvax watmath ]!clyde!rcj