From:	Isaac Waldron <waldroni AT lr DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: wierd problem in Allegro 3.0
Date:	Wed, 15 Apr 1998 17:38:09 -0400
Organization:	The Computer Nerd
Lines:	39
Message-ID:	<353528C1.38613512@lr.net>
References:	<353362C2 DOT 5556 AT cc DOT umanitoba DOT ca> <01bd6876$1b9633a0$3df706c3 AT mbizon DOT nordnet DOT fr>
Reply-To:	waldroni AT lr DOT net
NNTP-Posting-Host:	mere1-2.worldpath.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Maxime wrote:
> 
> I've got the same problem with Allegro 3.0. According to the debugger, the
> problem comes from the set_gfx_mode function.
> Please help us.
> 
> Count Razumovsky <umyumm AT cc DOT umanitoba DOT ca> a écrit dans l'article
> <353362C2 DOT 5556 AT cc DOT umanitoba DOT ca>...
> > I'm experiencing a very strange problem in Allegro that I hope someone
> > can shed some light on.  I'm using Allegro 3.0 with the newest versions
> > of djgpp and rhide.  All my programs compile and link fine but when I
> > try to run the executable the program dies and I get this message:
> >
> > Shutting down Allegro
> > Exiting due to signal SIGSEGV
> > Page fault at eip=000028b8, error=0004
> > .
> > .     (* very cryptic letters and numbers in here *)
> > .
> > call frame traceback EIPS:
> > 0x000028b8
> > 0x0002d20a
> >
> > What does that mean?? Only some of the program's which use allegro give
> > me this error, not all of them.  Has anyone seen this error before and
> > if so how do you fix it???    Thanks.
> >

I would suggest compiling your source with the -g option, which will
give you the line number and function of the crash when it occurs and
you run symify after.

-- 
==============================================================
   /\       Isaac Waldron
  /  \  /\  waldroni AT lr DOT net
 /    \/  \ http://www.geocities.com/SiliconValley/Lakes/3574/
/      \   \
==============================================================

- Raw text -