GNAT compiler problem?

[Rusnak <jrusnakzzz@netgate.net>]

I have been coding in Ada on a large project recently and until recently
have had little problems.  Unfortunately,
my program recenlty coughed up a Storage_Error which surprised me.
After removing my new code and putting it back
in piece by piece, I got a genuine segmentation fault.  I used gdb to
help analyze the code, and found that it was crashing on
a type definition.   (The actual compiler-mangled procedure name was
somethling like "my_package___read").  The type definition was a type
derived off
of a (base) tagged type.

I then set a breakpoint there and  reran the code.  After stepping
through the code after the first break, I found that the code execution
was going through an infinite loop
on  type definitions:  that is to say,    the call to
"my_package___read" (which the debugger indicated as originating from
the type
definition) called a procedure named something like
"base_package___read_2" (originating at the base class type
definition).  It then
called "my_package_read" again and so the cycle goes.    I assume that
the "read" is an internal procedure defined internally to the compiler,
since no such procedure exists in either of the packages (name mangling
in Ada by this compiler seems rather straightforward).

Has anyone seen this behavior before?

Thanks

-John