From: David Mikesell <dmikesell AT ee DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Seg fault
Date: Thu, 05 Feb 1998 22:55:20 -0500
Organization: eNET Inc. (Report Abuse to abuse AT ee DOT net)
Lines: 20
Message-ID: <34DA89A8.A51@ee.net>
References: <34DA8954 DOT 320 AT ee DOT net>
Reply-To: dmikesell AT ee DOT net
NNTP-Posting-Host: 209.190.33.42
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

...I'm also using Allegro 3.0

> 
> I'm using djgpp 2.01 on dos 6.22 and am trying to work through
> a particularly nasty seg fault bug.  I will purposely keep
> the problem statement general here, but will be happy to
> drill down to the source if nobody can point me in the right
> direction to begin looking.
> 
> I get the seg fault immediately after returning from a function
> that allocates memory...I can't seem to narrow the bug down to
> an offending pointer reference or a free() of a NULL pointer, etc.
> None of the malloc()'s returns a NULL pointer.  Any ideas
> on where to start looking?
> 
> --
> Dave Mikesell (dmikesell AT ee DOT net)

-- 
Dave Mikesell (dmikesell AT ee DOT net)