From:	"James Bunting" <james AT aic DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
References:	<370BAB46 DOT 6814 AT bellsouth DOT net>
Subject:	Re: allegro bugs
Date:	Wed, 7 Apr 1999 20:20:25 +0100
Lines:	30
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2014.211
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host:	warp8-52.enta-net.co.uk
Message-ID:	<370bb2a5.0@energise.enta.net>
X-Trace:	7 Apr 1999 20:31:49 -0100, warp8-52.enta-net.co.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I believe that Allegro will always shut down when a program crashes out.
The problem probably does not  lie with Allegro but with your code.  From
experience I have found that most crashes are caused by NULL pointers.  This
could be by assigning some data to a NULL or fixed pointer or simply my
writing to memory that you have not allocated.

A good way to find the error may be to run the program through RHIDE and see
if the frame traceback helps to point you to the right place in your code.
If this fails set up some kind of debugging code that lets you see how much
memory is free at a very regular basis and see if you are leaking the stuff.

It should also be noted that running under Win32 is often a lot more
tolerant of null pointers.  You should make sure that your program runs
under true DOS as well just to make sure that it all works.



seth <sethpark AT bellsouth DOT net> wrote in message
news:370BAB46 DOT 6814 AT bellsouth DOT net...
> Hi, i am trying to make little games and such with allegro but every now
> and then something will happen and my game crashes and says
> "shutting down allegro" ect.......
>
> Does anyone have any idea as to what type of code may cause that...
>
> thanks
>
> sad air

- Raw text -