Date: Wed, 6 May 1998 16:53:19 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Shue-Cheng CHEN <scchen AT ohriki DOT t DOT u-tokyo DOT ac DOT jp>
cc: djgpp AT delorie DOT com
Subject: Re: How to deal with my program crash?
In-Reply-To: <355022B3.7199D06A@ohriki.t.u-tokyo.ac.jp>
Message-ID: <Pine.SUN.3.91.980506164755.2627D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 6 May 1998, Shue-Cheng CHEN wrote:

> 	I don't know how to deal with my problem with the stack dump
> list. Please show me a way to do that. Thanks a lot! 
>
> Call frame traceback EIPs:
>   0x00051f26   _peek__7istream+80
>   0x00010b5c   _Comment__FR10istrstream+28, line 355 of func2.cc
>   0x000024e3   _main+535, line 56 of feappp2.cc
>   0x0006364a   ___crt1_startup+138

This says that on line 355 of the file func2.cc you called some library 
function which crashed.  The first thing to check in these cases is the 
arguments passed to that library function: look for uninitialized 
pointers, out-of-bounds references to arrays, etc.

> Exiting due to signal SIGSEGV
> Page fault at eip=00051f26, error=0004
> eax=00000002 ebx=000b39a8 ecx=000bff9c edx=00000000 esi=000b3f90 edi=000b3f34

This says that the crash happened because you tried to access an illegal 
address.  This also suggests uninitialized pointers are the cause.