X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=uvIXJyiMqhfoXzqRCPuvntx3+2vXONN7D485c+y1XA4=; b=hyDMtFZw7e37DgM1xOamxSxvdy2glUa10zawOztA0MbwFux4a+2bNeccd+vS9ek2zt B/CQDeVqbZXi9ZeU8VWuP0q0XNGgtXODBwHW9+FcIAhALFKSSJmugE3YrFXSIPgzJgKT tucJIVsMGOHu2zUJjXSGXGV1GEh0hKIefQLqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=FUrLjnNvTU/+XZCKSrf8i8MovsS1dbfilFUtd8bTM/Stbg/jV0IjeyDKn/1LoSaQFp XdZTG7lqzi9bPus/WS4ezfo39T6/onN86gCrNyyNHxrxc/suaTAD8IQD9C5F2yFycL5y vuiLok2dgr+VLXZZIyuUp1P1IU6UUzawRSmvI= MIME-Version: 1.0 Sender: gerritvn1945 AT gmail DOT com In-Reply-To: <7705c9030902100003x55552d4awb02e6d3597a28814@mail.gmail.com> References: <7705c9030902091323q48d59667x468b0c3bb0e4025f AT mail DOT gmail DOT com> <7705c9030902100003x55552d4awb02e6d3597a28814 AT mail DOT gmail DOT com> Date: Tue, 10 Feb 2009 10:19:48 +0200 X-Google-Sender-Auth: 35c7b04c597a4483 Message-ID: <9af855b0902100019t4e18f760sc9c8a228479393c0@mail.gmail.com> Subject: Re: DJGPP termios From: Gerrit van Niekerk To: djgpp AT delorie DOT com Content-Type: multipart/alternative; boundary=0015174c179690f42e04628c265c Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --0015174c179690f42e04628c265c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Tue, Feb 10, 2009 at 10:03 AM, Blair Campbell wrote: > > which is causing the crash. You can test to see if this is cause by > > disabling null pointer protection in DOS: before you run the test > > program enter: cwsdpmi -x > > For the next program (and only one program) the null pointer > > protection will be disabled. If the application then runs under DOS, > > it's a program bug that should be fixed. > > Ok yes, that is the problem then. Thanks for the hint. But it also > leads me to believe that the problem might be in ncurses because > dialog also crashes when using certain widgets. Any hints as to how > to find what is using a bad pointer? I'm not really familiar with > gdb. > It will be worth your while getting to know GDB. It will show you exactly where the bad pointer is. --0015174c179690f42e04628c265c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 10, 2009 at 10:03 AM, Blair Campbell= <blairdude AT gma= il.com> wrote:
> which is causing the crash.  You can test t= o see if this is cause by
> disabling null pointer protection in DOS:  before you run the tes= t
> program enter:  cwsdpmi -x
> For the next program (and only one program) the null pointer
> protection will be disabled.  If the application then runs under = DOS,
> it's a program bug that should be fixed.

Ok yes, that is the problem then.  Thanks for the hint.  Bu= t it also
leads me to believe that the problem might be in ncurses because
dialog also crashes when using certain widgets.  Any hints as to how to find what is using a bad pointer?  I'm not really familiar with=
gdb.

It will be worth your while getting to know GDB. It w= ill show you exactly where the bad pointer is.

--0015174c179690f42e04628c265c--