Article View: comp.os.msdos.programmer
Article #3866Re: Turbo C++ (Debugger bug?)
From: Joel Spolsky
Date: Wed, 12 Dec 1990 00:47
Date: Wed, 12 Dec 1990 00:47
17 lines
1348 bytes
1348 bytes
In article <25804@uflorida.cis.ufl.EDU> jdb@reef.cis.ufl.edu (Brian K. W. Hook) writes: >I have Turbo C++ 1.00 but have noticed that it has a couple of errors, ie. >bugs. Has anyone encountered the fact that the debugger REALLY screws up >when tracing code? It seems that it arbitrarily jumps to come code at >times that resembles other code... Hello, That is not a bug. What is happening is that the optimizer is rearranging your code so that it can be made smaller or faster. The debugger, admittedly, gets confused trying to map the binary reality to the source code ideal... When you want to debug, you should just turn off all optimizations. Joel Spolsky spolsky@cs.yale.edu Silence = Death
Technical Details
Message-ID:
<27741@cs.yale.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cs.yale.edu!spolsky-joelReferences:
<25804@uflorida.cis.ufl.EDU> <1990Dec11.222033.21473@isis.cs.du.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cs.yale.edu!spolsky-joel From: spolsky-joel@cs.yale.edu (Joel Spolsky) Newsgroups: comp.os.msdos.programmer Subject: Re: Turbo C++ (Debugger bug?) Keywords: reentrant routines Message-ID: <27741@cs.yale.edu> Date: 12 Dec 90 00:47:22 GMT References: <25804@uflorida.cis.ufl.EDU> <1990Dec11.222033.21473@isis.cs.du.edu> Sender: news@cs.yale.edu Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158 Lines: 17 Nntp-Posting-Host: thai-gw.cs.yale.edu Originator: spolsky@thailand.CS.Yale.Edu