home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!usc!sdd.hp.com!apollo.hp.com!netnews
- From: nelson_p@apollo.hp.com (Peter Nelson)
- Subject: Is it really this bad or is it just me II
- Sender: usenet@apollo.hp.com (Usenet News)
- Message-ID: <Bs3nL9.5zE@apollo.hp.com>
- Date: Tue, 28 Jul 1992 12:48:44 GMT
- References: <Bs3Mpp.5ML@apollo.hp.com>
- Nntp-Posting-Host: c.ch.apollo.hp.com
- Organization: Hewlett-Packard Corporation, Chelmsford, MA
- Lines: 43
-
-
-
- I recently posted a long article about trouble debugging
- scrolling messages in Borland's (3.1) TDW. ( To recap: I seem
- to get multiple scrolling messages for a single click on the
- scrollbar when I'm in TDW but no strange behavior when I'm
- not in TDW.)
-
-
- So I thought I'd study the problem with Winsight (Borland's
- "passive" message and other event viewer). But if I try to
- run my program when Winsight is running my program does a
- GPF with Exception 13 (address violation)!! It's fine when
- Winsight is not running. According to TDW the exception is
- happening in a call to TextOut.
-
- So I tried running Petzold's "Hello Windows" program, which
- is about as simple and safe a Windows program as there is,
- while Winsight was on. It didn't crap out totally, but
- instead of displaying "hello windows" it displayed gobbledygook
- ( probably Martian for "you're screwed, pal!" )
-
-
- So what's the deal here? If tiny, simple beginner's programs
- crap out with Borland's debugger and Winsight, then how the HELL
- does anyone develop and debug any nontrivial apps with these things??!!
-
- Are the Microsoft tools any more reliable than this?
-
- Thanks for any comments and advice.
-
-
- ---peter
-
-
- PS -- Gateway 2000, 486/33, 8M RAM, DOS 5.0, Windows 3.1,
- Borland C/C++ 3.1, Microsoft serial mouse using the
- driver supplied with Windows 3.1, TDW is running in
- dual monitor mode.
-
-
-
-
-