Conference tallis::alpha_migration_tools

965.0. "VEST: native exe calling xlated shareable gives 'opcode reserved to Digital'" by GALVIA::DUKE (Ronan) Mon Apr 28 1997 12:10

Hi,
  I'm having a problem running a native AXP image that calls a translated
shareable.

  At the moment, I have a translated shareable that works fine.  I can test it 2
ways:
 1.  by calling it from a translated image (where the original VAX image was 	
    linked with the original VAX version of the shareable)
 2.  by calling it from a native ALpha image by doing cc/tie and link/nonative.

  In response to a customer problem, I have added a few more lines of code to
the shareable and re-VESTed it.
  I now find that test 1 above still works.  However, test 2 fails (see output
below).
  What appears to be happening is that the routine in the translated shareable
image is not being called (i have a print statement as the first line).  It
looks like there's a problem in getting to that function ?

   IMBUSY > run rusl/nodeb

CAlling start application:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0002FFFE,
PC=0059E400, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
 Image Name   Module Name     Routine Name    Line Number  rel PC      abs PC
 VMS$IEEE_HAN                                           0 00030400    0059E400
----- above condition handler called with exception 0000043C:
%SYSTEM-F-OPCDEC, opcode reserved to Digital fault at PC=00030002, PS=0000001B
----- end of exception message
                                                        0 9EEE82BC    9EEE82BC
 RUSL         RUSL                                      0 00020002    00030002
----- Begin Translated VAX Frames
 TIE$SHARE                                              0 00058F04    003FAF04
----- End Translated VAX Frames
                                                        0 9F00733C    9F00733C
 RUSL         RUSL            main                   8047 00000128    00020128
 RUSL         RUSL            __main                    0 00000054    00020054
                                                        0 9F008170    9F008170


  However, as I've stated, this works fine when called from the translated image
- all my print statements give output.

  I don't have the SIF file for my first version of the translated shareable
image.  I'm using one now which has the same symbol order as the VAX link
options file (except for the 'spare' at the top).  However, with the native exe,
i'm linking and running against the same translated shareable
  BTW, The application is a very large old one, written in BLISS. 
  The images were build on a VAX/VMS V6.1 system.  They were VESTed on Alpha/VMS
V6.2.   
  I'd include the LIS file but it's 3k+ blocks !
  I've checked the Translating Images manual /suggestions and I don't see
anything that helps.

Am I missing something obvious ?

thanks for any help,
-ronan

     Image Identification Information

                image name: "VEST_TV"
                image file identification: "V1.1A-0"
                link date/time: 13-OCT-1994 11:12:46.83
                linker identification: "V1.1A-0"

If you look at section 6.2.3 of the Translating Images Guide, you'll
see a couple things:  first, you can use VEST to create a SIF file
for you, and second, in some cases you may need to leave the first
SYMBOL_VECTOR=entry SPARE for compatibility with the translated
version of the shareable image.

Basically, I think if you put the SPARE back in at the top you'll
probably be okay.  If you still have problems, read through that
section.  The Guide goes through step by step what you need to do
to get this to work (my guess is though that what I've suggested
will fix your problem).


Brian

Brian,
  I had read section 6.2.3 and I had created a .SIF file. 

  However, it turns out that my SIF file was imcomplete.  I had deleted a line
by accident which I only discovered today by re-running VEST/SIF/NOEXE, running 
SIF2OPT on both SIFs and doing a diff of the options files.

  Once, I recreated the .SIF file, everything worked OK.

-ronan

Oh!  Well, glad you got it fixed.


Brian