Message-ID: <3439CF81.4067@post.comstar.ru>
Date: Tue, 07 Oct 1997 08:58:25 +0300
From: Dim Zegebart <zager AT post DOT comstar DOT ru>
Reply-To: zager AT post DOT comstar DOT ru
Organization: Comstar Ltd.
MIME-Version: 1.0
To: Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>
CC: DJGPP Mail List <djgpp AT delorie DOT com>
Subject: Re: Strange problem
References: <34390D16 DOT 2C21 AT post DOT comstar DOT ru> <343934CB DOT 23715EBF AT LSTM DOT Ruhr-UNI-Bochum DOT De>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Thomas Demmer wrote:
> Are you sure you call malloc with an arguement > 0 and < pretty large?
I'm hardly coded 428 byte to allocate.
> As your program seems to die inside malloc(), I'd guess you feed some
> junk into malloc(). Although after a quick glance into malloc I cannot
> see why it should choke on negative or 0 arguements, but then again,
Moreover, my programm may crash at strdup() then it calling malloc() or
at calloc() at the same situation. I'm using Allegro with interrupts
handler
installed and extend it to handle comm ports. May be it is the point of
truble ? I mean something wrong happens then two or more int occures
simultaneosly and one of them handled at real mode code by BIOS, so
stack
damage can occures then returning from protected mode handler ?

-- 
Regards,
Dim Zegebart, 
Moscow Russia.
Ghostly basement : http://www.geocities.com/siliconvalley/pines/7817
DZCOMM - comm library for Allegro