From: Richard Dawe <richdawe AT bigfoot DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: K6-2 500
Date: Wed, 15 Nov 2000 23:32:49 +0000
Organization: Customer of Energis Squared
Lines: 29
Message-ID: <3A131D21.4B5C4380@bigfoot.com>
References: <3a129b6b$0$15996 AT SSP1NO25 DOT highway DOT telekom DOT at>
NNTP-Posting-Host: modem-133.silicon.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news7.svr.pol.co.uk 974331585 523 62.136.13.133 (15 Nov 2000 23:39:45 GMT)
NNTP-Posting-Date: 15 Nov 2000 23:39:45 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586)
X-Accept-Language: de,fr
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello.

Florian X wrote:
> I am constribute to the SEAL project and read an error in the forum:
> 
> It is ___only____ on K6-2 500 CPU:
> 
> Shutting down Allegro
> Exiting due to signal SIGSEGV
[snip]
> Call frame traceback EIPs:
> 0x5f746567
> 0x00013988
> 0x000211db
> 0x00021a47
> 0x000a8192
> 
> Is this an bug of DJGPP/ALLEGRO or of SEAL?

What happens if you run symify on your program? You may need to rebuild
with debug information, before symify lists function names.

FWIW I never had an error on a K6-2 400MHz with DJGPP.

Bye,

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]