Re: Howto debug seg-faulting Ada 95 code?

["Jeffrey Creem" <jeff@thecreems.com>]

"Pat Rogers" <progers@classwide.com> wrote in message
news:asSc9.5091$Ss7.1261527110@newssvr30.news.prodigy.com...
> >
> > Having said that, every compiler I have used does something like
> this.  It
> > also tends to
> > make intuitive sense.
>
> Humm, every compiler I have used did not.  Declarations within library
> units are just the first things pushed. We don't think of that initial
> stack push as being a stack operation because it is never "popped"
> until the program completes.
>
>

Well, as I said there is nothing in the LRM that I know of that requires
either behaviour so
it is certainly possible that you are correct.

Another poster was more precise when he said he sees x86 compilers put these
in the
data segment (initialized or uninitiazed).

The compiler I have seen which put package level variables "not on the
stack" are

VADS -> 68K vxWorks
VADS -> MIPS vxWorks
VADS -> PowerPC vxWorks
Apex -> Solaris
GNAT -> Solaris
GNAT -> win32/linux

It seems like a strange convention to allocate package level variables on
the stack. It now means
that in a multi-tasking program you have tasks mucking in the stack of
another task.... Again, no reason
that I can think of that this would not work but it does feel odd.