From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1094ba,72599d70c71acec3,start X-Google-Attributes: gid1094ba,public X-Google-Thread: 103376,72599d70c71acec3,start X-Google-Attributes: gid103376,public From: "James Giles" Subject: Semantics of "halting immediately" was (F9X twister, etc...) Date: 2000/04/12 Message-ID: #1/1 X-Deja-AN: 610440607 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 X-Complaints-To: abuse@worldnet.att.net X-Trace: bgtnsc04-news.ops.worldnet.att.net 955583370 12.74.2.27 (Wed, 12 Apr 2000 23:49:30 GMT) Organization: AT&T Worldnet NNTP-Posting-Date: Wed, 12 Apr 2000 23:49:30 GMT Newsgroups: comp.lang.fortran,comp.lang.ada Date: 2000-04-12T00:00:00+00:00 List-Id: Geoff Bull wrote in message <38F41313.DAF90E74@research.canon.com.au>... ... >> And, >> branching to a handler probably loses all of the register contents >> that were present when the error arose. >I'm missing something. >By my definition of quit immediately you lose the contents of registers too. Those are (should be) in the drop-file, core file, or whatever is generated on your system that the debugger gets to look at when a program abnormally terminates. If the program continues to run after the error is detected, this information reflects the state the program is in when it does finally terminate (ie. after "graceful" termination). >> The buffers are inside the system and not part of my process >> image anyway. Systems which >> throw away I/O buffer information when a process terminates >> are seriously broken. > >What about buffered io and user defined buffering? Like all parts of the program's state, those are all still present in the debugging file. You can inspect them there. If you're writing a program and testing its operation (or even just using it, but you're also the one that wrote it) you want the program halt in the case of an error without destroying the evidence of what caused the failure. -- J. Giles