LEICHTER-JERRY@YALE.ARPA (03/04/86)
We have a ... shareable image ... linked to a lot of our ... programs.
Since converting from VMS 3.6 to 4.0 some of these programs have been
acting strangly. e.g. - going into infinite loops, or bombing on
'reserved operand fault' ... where the program makes a call to the VMS
Run-time library. e.g.- LIB$GET_FOREIGN. The problem goes away if we
link the program with .OBJ files instead of the shareable image.
N.B. - We didn't use any fancy LINK options when we created the
shareable image, only "UNIVERSAL=name" and "GSMATCH=ALWAYS,0,0".
...
Have you re-linked the shareable image since you converted? The errors you
are describing make it sound as if control is being transfered to some random
location in the code - a likely result if entry points moved but the calls to
them still point to the old addresses.
Normally, entry vectors, once created, don't move so that old programs will
continue to work without re-linking on new systems. (That's why entry vectors
exist in the first place.) There must be something odd in your particular
configuration. Making your private shared image BASED could probably cause
this problem.
Note that you've asked for this kind of by including GSMATCH=ALWAYS; the whole
purpose of GSMATCH is to tell you when things might have changed.
-- Jerry
-------