delorie.com/archives/browse.cgi | search |
From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Program crashes once, runs once, crashes, runs, crashes, runs, etc. |
Date: | Wed, 20 Oct 1999 17:56:34 |
Organization: | Aspen Technology, Inc. |
Lines: | 7 |
Message-ID: | <380e0252.sandmann@clio.rice.edu> |
References: | <cnINOE3q0a2g85mZ8CyTQU0r9wE5 AT 4ax DOT com> |
NNTP-Posting-Host: | dcloan.aco.aspentech.com |
X-NewsEditor: | ED-1.5.8 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> I ran her again (same code, same inputs), and she ran fine. So I ran her again > (same code, same inputs), and ths time she crashed. And so on. Uninitialized variables using uninitialized memory. It has something different in it each time. Look at the symify of the traceback and see which variable could cause the crash.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |