home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: sci.image.processing
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!rouge!twc
- From: twc@swamp.cacs.usl.edu (Tat W. Chan)
- Subject: Debugging problem
- Message-ID: <1993Jan26.012844.15569@usl.edu>
- Followup-To: twc@swamp.cacs.usl.edu.usa
- Sender: anon@usl.edu (Anonymous NNTP Posting)
- Organization: The Center for Advanced Computer Studies
- Date: Tue, 26 Jan 1993 01:28:44 GMT
- Lines: 17
-
- Hi,
-
- I would like some comments about some problems that I encountered recently.
-
- 1. Debugging a large program which input data is huge and not
- well-structured (as it is common in the domain of this newsgroup),
- is there any effective ways to locate the bugs? Should we deal with
- the program first, or the data first, or both?
-
- 2. If there is any good way to solve #1, is it different from debugging
- techniques in other domains in which the input data is not so intensive?
-
- Thanks for any help in advance!
-
-
-
-
-