Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!DECVAX.DEC.COM!vasudev
From: vasudev@DECVAX.DEC.COM
Newsgroups: comp.windows.x
Subject: Re: server debugging
Message-ID: <8802291359.AA01925@flume.dec.com>
Date: 29 Feb 88 13:59:49 GMT
References: <8802242206.AA10721@siesta.megatek.uucp>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16



Our experience has shown that dbx itself is not a perfect example
of robust code either.  Dbx barfs on very large object modules with
a large number of symbols with and ->Internal Table Overflow<-
or by just plain lying about what its doing.  We have had the good
luck of being supported by an outstanding engineer who has fixed
many bugs in dbx.  

To get back to Server Debugging, we have also found it very useful
to identify specific modules within the server that you guess to be
bogus and then compile those with the -debug option.  dbx works wonderfully
in such cases.

When all else fails, there ain't nuttin' like good ole printf.

-Vasudev