NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/lang/cplus/16361

Internet Message Format | 1992-11-16 | 1.8 KB

Xref: sparky comp.lang.c++:16361 comp.std.c++:1574
Newsgroups: comp.lang.c++,comp.std.c++
Path: sparky!uunet!pmafire!mica.inel.gov!ux1!news.byu.edu!gatech!concert!sas!mozart.unx.sas.com!sasghm
From: [e-mail] (Gary Merrill)
Subject: Re: something nasty report
Originator: [e-mail]
Sender: [e-mail] (Noter of Newsworthy Events)
Message-ID: <[e-mail]>
Date: Mon, 16 Nov 1992 15:50:23 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]>
Nntp-Posting-Host: theseus.unx.sas.com
Organization: SAS Institute Inc.
Lines: 21


In article <[e-mail]>, [e-mail] (James A. Mullens) writes:

|> When I'm faced with an access violation/segmentation violation/bus error,
|> and I really have no clue as to what's causing it, I start removing large
|> blocks of source code with #if 0 ... #endif until the compiler finishes
|> successfully.  Then I reintroduce parts of code until the compiler bombs
|> again.  In the end, the problem is isolated.  I may have a programming
|> error there, or the compiler may just be batty.  I always send a bug report.
|> I'd like to send a bill for my time ( at $60/hour :-).

Pretty irritating, isn't it?  Certainly *we* expect to receive a bug report
if our compiler behaves in this way -- and having someone pinpoint the
problem with a test case of a finite number of lines is heavenly.
If you don't have debuggable version of the compiler (and most production
versions aren't), these things are *hard* to find.  $60/hr would be
a bargain.
--
Gary H. Merrill  [Principal Systems Developer, C Compiler Development]
SAS Institute Inc. / SAS Campus Dr. / Cary, NC  27513 / [phone]
[e-mail] ... !mcnc!sas!sasghm