home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!sgigate!odin!homebrew.asd.sgi.com!foulser
- From: foulser@homebrew.asd.sgi.com (David Foulser)
- Newsgroups: comp.graphics.explorer
- Subject: Re: debugging in module builder
- Message-ID: <1993Jan22.020831.7222@odin.corp.sgi.com>
- Date: 22 Jan 93 02:08:31 GMT
- References: <1993Jan21.205947.18732@alw.nih.gov>
- Sender: news@odin.corp.sgi.com (Net News)
- Reply-To: foulser@homebrew.asd.sgi.com (David Foulser)
- Organization: sgi
- Lines: 21
- Nntp-Posting-Host: homebrew.asd.sgi.com
-
- I assume you mean debugging an Explorer module you built with mbuilder.
- You can use dbx, just say
- dbx -P <moduleName>
- for instance
- dbx -P GenerateColormap
-
- (of course, our modules are stripped, so debugging them won't helpmuch).
-
- You could also use cvd, the WorkShop debugger.
-
- You can make sure your modules are compiled -g by setting the environment
- variable DEBUG to something non-null, like 1.
-
- Dave
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- David Foulser foulser@sgi.com
- MS 1L-545
- Silicon Graphics, Inc 415/390-5338
- 2011 N. Shoreline Blvd. 415/390-6056 FAX
- Mountain View, CA 94039-7311
-