RE: STORAGE_ERROR : EXCEPTION_STACK_OVERFLOW

["Robert C. Leif" <rleif@rleif.com>]

   Marius Amado Alves wrote, "isn't it possible that your program has a
logic fault that is exhausting that stack?"
   Since the original version with 16 bit pixels works and a new version
with 16 bit pixels and an access type for the two dimensional array works,
the existence of a logic fault that exhausts the stack is highly unlikely.
The access type version with 32 bit pixels executes.  However, there appears
to be a problem with the creation of the normalized images, which have 8 bit
pixels.  These 8 bit pixel images are critical because the dynamic range of
the human eye while looking at an image is of the order of 8 bits.
   The real problem is that I can not use a standard, simple data-type (a
two dimensional array) for my program, which could be eventually used in a
medical device.  I am presently forced to increase the complexity of my
program by the use of access types and consequently have decreased its
safety. 
   Hypothetically, if I find a sponsor with adequate funding to
commercialize this research technology, the next step would be to use SPARK,
which does not include access types.  I suspect that there is a reasonable
consensus amongst the readers of Comp.Lang.Ada that Ada and SPARK are
excellent choices for medical imaging.  Therefore, it would be very useful
to either create large objects on the stack or have the compiler put them on
the heap while maintaining the relatively simple syntax of a two dimensional
array type.  In short, the compiler should permit me to maintain the
abstraction.  Obviously under these circumstances, the use of a pragma would
be acceptable. Is there anything to be learned from Java technology where it
appears that simple data-types are put on the heap?
   Bob Leif
   
   ------------------------------------------------------------------
   Date: Sat, 9 Jul 2005 10:27:55 +0100
   From: Marius Amado Alves <amado.alves@netcabo.pt>
   Subject: Re: STORAGE_ERROR : EXCEPTION_STACK_OVERFLOW
   To: Robert C.Leif <rleif@rleif.com>
   Cc: "Comp. Lang. Ada" <comp.lang.ada@ada-france.org>
   Message-ID: <0374b45e755cd2faa7be393083f5d669@netcabo.pt>
   Content-Type: text/plain; charset=US-ASCII; format=flowed
   
   What does this message mean EXCEPTION_STACK_OVERFLOW?
   
   If it means overflow of a stack of exceptions, then isn't it possible 
   that your program has a logic fault that is exhausting that stack?
   
   ------------------------------