delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/09/10/03:50:39

X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs
Date: Fri, 10 Sep 1999 10:20:07 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: djgpp AT delorie DOT com
cc: Andy <wowbagger AT diamond DOT co DOT uk>
Subject: Re: Need help building Allegro!?!
In-Reply-To: <Pine.SUN.3.91.990909091820.6646G-100000@is>
Message-ID: <Pine.A41.4.05.9909101008430.53916-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com


On Thu, 9 Sep 1999, Eli Zaretskii wrote:

> 
> On Wed, 8 Sep 1999, Andy wrote:
> 
> > I am having a similar problem, I use djgpp 2.02 with gcc/gpp 2.95.1 bnu
> > 2.8.1, and I get a variety of crashes (Internal errors, SIGSEV errors), in
> > various departments, sound and grafix (twice in mixer.c)
> 
> No, this is a totally different case, see below.
> 
> > Exiting due to signal SIGSEGV
> > General Protection Fault at eip=0054779b
> > eax=0000005f ebx=00547774 ecx=00000007 edx=00000000 esi=00000000
> > edi=00000000
> > ebp=00323a5d esp=00333958
> > program=C:\UTILS\DJGPP\LIB\GCC-LIB\DJGPP\2.951\CC1.EXE
>                                                  ^^^^^^^
> See?  The program that crashed is cc1.exe, the C compiler.  The
> original message that started this thread talked about an Allegro
> program that crashed, not the compiler.

At first You can use symify on
C:\UTILS\DJGPP\LIB\GCC-LIB\DJGPP\2.951\CC1.EXE

It contains info about functions. So You'll be able to get 
stack trace. I compiled gcc-2.95 with -O2 (no debug info) but didn't 
strip the executables, so symify must give function names

I left this info in (loss in space is not so large I think) as
previous experience showed that later it's difficult to exactly reproduce
the same binary.

Of course if You stripped cc1.exe Youself then You NOT to stubedit it
to enlarge stack after stripping (eg. stubedit cc1.exe minstack=1536k)

Possible reasons of such crash:
	- bad hardware (most likely, I think). If CPU is overclocked
          please recheck without overclocking)
	- broken DPMI server (should not be with CWSDPMI or under
	  Win9X or WinNT)
        - stripped cc1.exe but it's not stubeditted after that
          to increase stack and one is compiling large source file 
	

> >   0x0054779b
> > make.exe: *** [obj/djgpp/mixer.o] Error 1
> > 
> > Sorry no data from symify
> 
> This is normal: DJGPP binaries distributed in the zip files are
> stripped of the debugging symbols, so SYMIFY won't find anything.
> 
> > not much time now and I do not know how to use
> > the program yet, I have not found the docs
> 
> Section 9.2 of the FAQ tells you how to use SYMIFY.
> 

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019