Storage error

Storage error

[Scott Sheffield]

I have a program that is compiling and building fine but draws a storage
error when it is run. I tried pragma suppress(storage_check) to try to
force it to run but it still raised a storage error. I'm not entirly
clear on what this is telling me and I have no idea how to resolve this
issue. Any help would be appreciated.

Scott

Re: Storage error

[Stephen Leake]

Scott Sheffield <sheffieldsy@lmtas.lmco.com> writes:

> I have a program that is compiling and building fine but draws a storage
> error when it is run. I tried pragma suppress(storage_check) to try to
> force it to run but it still raised a storage error. I'm not entirly
> clear on what this is telling me and I have no idea how to resolve this
> issue. Any help would be appreciated.
> 
> Scott

Storage_Error means something is running out of memory; either heap or
stack. You may be declaring an unconstrained object with a huge index
(see the recent series of messages). You may have your stack size too
small. Or you may be doing something else. You'll have to post code to
get more help. Please include compiler brand and version, and OS brand
and version.

-- Stephe

Storage Error

[Tom Gargulak]

I got the following example from the book by Barnes (pg. 183).  Barnes 
claims that this program should raise the STORAGE_ERROR exception
and I agree due to 11.4.1(10) in the LRM.  A colleague believes that
Barnes is mistaken and that it would be acceptable for the program
to run forever.  He claims it depends how the stack is implemeted.

Barnes claims the following should happen:


    |		n-3	B				H	
    |		n-2	B		H		B
    |		n-1	B	H	B	H	B
    V		n	*	*	*	*	*

Invocation	--------------------------------------->time

B - executing in the procedure body for invocation n-m
H - executing in the exception handler for invocation n-m
* - a call which failed due to STORAGE_ERROR


Does anyone know what should happen and why?


Thanks,
Tom

--------------------------------cut here----------------------------

procedure P is
begin
  P;
exception
  when others =>
    P;
end;

Re: Storage Error

[Brian Hanafee]

In article <108637@convex.convex.com> gargulak@mozart.convex.com (Tom Gargulak) writes:
>I got the following example from the book by Barnes (pg. 183).  Barnes 
>claims that this program should raise the STORAGE_ERROR exception
>and I agree due to 11.4.1(10) in the LRM.  A colleague believes that
>Barnes is mistaken and that it would be acceptable for the program
>to run forever.  He claims it depends how the stack is implemeted.
[stuff deleted]
>
>procedure P is
>begin
>  P;
>exception
>  when others =>
>    P;
>end;


I believe that there are three possible (implementation dependent)
behaviours for this program:

Case 1:
  The compiler generated code does not require any new storage for
each new invocation of P.  In this case, the program will not run out
of storage, and may acceptably run forever.

Case 2:
  If the implementation requires that each invocation of P uses some
new storage (such as stack space), then eventually an invocation of P
will cause a STORAGE_ERROR.  The invocation of P from the handler will
(presumably) cause a *new* STORAGE_ERROR to be raised.  Under
11.4.1(10), this exception will cause the program to raise
STORAGE_ERROR.

Case 3:
  After STORAGE_ERROR is first raised, the program could detect that the
invocation of P from the handler is erroneous, and raise PROGRAM_ERROR
instead.


------------------------------------------------------------------------
Brian Hanafee                    | **Standard Disclaimer**
Advanced Decision Systems        |
------------------------------------------------------------------------

Re: Storage Error

[Tom Gargulak]

[oops again]

One thing I failed to mention.  I assume that the program will raise
a storage_error exception due to the infinite recursion.  I realize
some compilers can optimize this into a loop.

So, assuming the exception occurs, will this program eventually 
terminate?  Why?

Thanks again,
Tom