[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::alphanotes

Title:	Alpha Support Conference
Notice:	This is a new Alphanotes, please read note 2.2
Moderator:	VAXAXP::BERNARDO

Created:	Thu Jan 02 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	128
Total number of notes:	617

33.0. "Image Activation and R9" by GALVIA::FOX_F () Mon Jan 27 1997 07:12

    
    I am currently porting a VAX MACRO application to ALPHA and I have 
    encountered an access violation when running the program. The violation 
    involves the R9 register which contains an address of 7FF9C400.
    
    This value is in R9 from the very start of the program and all programs 
    that I start on my system seem to have this value in R9. Does image 
    activation on Alpha put anything in particular into R9 ?

T.R	Title	User	Personal Name	Date	Lines
33.1		EEMELI::MOSER	Orienteers do it in the bush...	`Mon Jan 27 1997 07:29`	12
	you should not be concerned with any registers the image activator touches. R9 is a non-scratch register. Are you correctly saving/restoring non-scratch register you use? are saving /restoring all 64-bits of registers? Is the accvio in a calls routine or in a jsb routine? Can you post the traceback info and maybe a small code fragment around the accvio? /cmos
33.2	Passing args via CALLx stack _and_ R9?	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Jan 27 1997 09:53`	11
	This looks like an uninitialized register, or an, uh, unusual calling sequence -- see if the code is using both a CALLx interface, and expects specific values placed into registers (such as R9) by the calling routine to be available in the CALLx'd routine... If this is the latter case, I'd reimplement the calling sequence slightly. Example code would help... And TURRIS::MACRO is another spot for these questions...