Article View: comp.sys.ibm.pc.misc
Article #3207Re: When CTRL+C doesn't work.
From: Raymond Chen
Date: Fri, 14 Sep 1990 22:35
Date: Fri, 14 Sep 1990 22:35
12 lines
998 bytes
998 bytes
In article <6241@castle.ed.ac.uk> elee24@castle.ed.ac.uk (H Bruce) writes: > This is a very time consuming way to find bugs ! Everybody seems to be missing the forest but for the trees here... The real question is not about trapping Ctrl+C, but rather "How do I debug my program if it gets caught in a tight loop?" The answer is to run your program *under a debugger*. You get lots of other benefits, like being able to inspect variables at the point the program hangs. All the major compilers come with debuggers. Use them.
Technical Details
Message-ID:
<1990Sep14.223544.9782@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!snorkelwacker!apple!agate!usenetReferences:
<6241@castle.ed.ac.uk>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!snorkelwacker!apple!agate!usenet From: raymond@math.berkeley.edu (Raymond Chen) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: When CTRL+C doesn't work. Message-ID: <1990Sep14.223544.9782@agate.berkeley.edu> Date: 14 Sep 90 22:35:44 GMT References: <6241@castle.ed.ac.uk> Sender: usenet@agate.berkeley.edu (USENET Administrator) Reply-To: raymond@math.berkeley.edu (Raymond Chen) Organization: U.C. Berkeley Lines: 12