Xref: news2.mv.net comp.os.msdos.djgpp:1870
From: moliger AT iccom DOT com (Mark L. Oliger)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problem with Executable - post [01/01]
Date: Wed, 13 Mar 96 01:03:07 GMT
Organization: Internet Communications
Lines: 45
Message-ID: <4i5had$57e@zzz.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960311124617 DOT 4975E-100000 AT is>
NNTP-Posting-Host: ppp-6.pdx1.zzz.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <Pine DOT SUN DOT 3 DOT 91 DOT 960311124617 DOT 4975E-100000 AT is>,
   Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>
>On Fri, 8 Mar 1996, Mark L. Oliger wrote:
>
>> Program received signal sigsegv, segmentation fault.
>> 0x67cc in _flsbuf()
>> 
>> Here is what I get when I run it (I don't understand any of this):
>> 
>> 
>> Exiting due to signal SIGSEGV
>> Page fault at eip=000067cc, error=0006
>> eax=00000000 ebx=ffffffff ecx=00008734 edx=00000070 esi=00000000 
edi=00008734
>> ebp=00046998 esp=00046988 cs=00e7 ds=00ef es=00ef fs=00cf gs=00ff ss=00ef
>> Call frame traceback EIPs:
>>   0x000067cc
>>   0x00004582
>>   0x000020a9
>>   0x0000172d
>>   0x0000163e
>>   0x00001c67
>
>Compile your program with -g switch.  Then re-run it to get the above 
>traceback.  Now, while the traceback is still on screen, type the 
>following words of wisdom:
>
>	symify printit
>
>The little wonder called `symify' will magically put the source file 
>names and line numbers near each of the addresses in the traceback.  You 
>will then see what source line of your program caused the error.
>
>Compiling with -g will also help you run under the debugger.  You will be 
>able to step through source lines, print variables and otherwise make a 
>nuisance out of yourself.
>
>There are more details on this in the DJGPP FAQ list, section 9.2 and
>chapter 12, which I suggest you read.  The FAQ is available as
>v2/faq200b.zip from the same place you get DJGPP. 

Thanks for your reply.  I will try this, and read further into the FAQ.  

Mark