Xref: news2.mv.net comp.os.msdos.djgpp:714
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Issues with nearptr's.
Date: Mon, 29 Jan 1996 21:10:17 CST
Organization: Rice University, Houston, Texas
Lines: 10
Message-ID: <310d8c19.sandmann@clio.rice.edu>
References: <822855248snz AT trenham DOT demon DOT co DOT uk> <310c0125 DOT sandmann AT clio DOT rice DOT edu> <4eccdl$90b AT clarknet DOT clark DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> I've written a couple of graphic routines with nearptrs and they run fine 
> under dos and cwsdpmi, but when I try to run them under gdb, I get a 
> segmentation violation signal.  

I believe you, I've never tried it.  Does it work under EDEBUG32 or FSDB?
If so, it may be some bug in GDB's memory management or something.  Are
you sure you are using the non-move sbrk()?  This is exactly the problem
I would expect using a debugger and the unix-sbrk with nearptrs (unless
you reload the pointer).  A simple example is most useful debugging these
problems.