generic provokes segmentation fault

[hreba <f_hreba@yahoo.com.br>]

Hi,

I'll try to describe the problem without posting loads of code. Still 
working on my thick binding of GSL/Odeiv2, the API of my package odeiv2 
consists of 3 procedures:
  - Init_Solve
  - Solve
  - Finit_solve
They basically copy values to variables which are global in odeiv, and 
pass their addresses to the C library functions of the thin binding. 
Example: Solve contains

status:= Gsl.gsl_odeiv2_driver_apply
	(solver.driver, solver.t1'Access, solver.t2,
	 solver.y(solver.y'First)'Access);

solver is a global record variable with components t1, t2 of type 
C.double, and solver.y of type

    type C_Array is array (Integer range <>) of aliased C.double;
    pragma Convention (C, C_Array);

The main program calls Init_Solve once, then Solve a hundred times, and 
finally Finit_Solve. It works and calculates the correct numbers. Now 
when I make odeiv generic:

generic
    dim:	Positive;
    type Float is digits<>;
package odeiv2 is
...

and substitute in the main program

    package Ode renames odeiv2;

with

    type Real is digits 6;
    package Ode is new odeiv2 (2, Real);

and change nothing else, I get a

raised STORAGE_ERROR : stack overflow or erroneous memory access
(SIGSEV, segmentation fault, when run under the debugger)
just at the line starting "status:= ..." shown above.
What would be an explication or a remedy for this behaviour?

-- 
Frank Hrebabetzky, Kronach	+49 / 9261 / 950 0565