On Wed, 2 Apr 1997, Mats O Jansson wrote:

> I looked at the code. And mopd hard codes loadaddr to 0 even in the a.out
> case. So patching mopa.out or GetAOutFileInfo is a matter of choies.
> 
> But looking on both ISL_LVAX_061.SYS and ISL_SVAX_061.SYS loadaddr is 0x200
> or 0x0. Even VXT-images is loaded at 0. All this images should overwrite
> the SCB if that is the problem.
> 
> Could I get a copy of your image with a halt added after relocaded: in 
> srt0.o? This to be able to single step through the code, I have found 
> the cause of several SCB2NDINT this way...


I have noticed a few relocation problems with VAXlinux (I am in fact 
using a modified NetBSD srt0.s).. The problem I've seen is that the SCB 
doesn't seem to load where it should, ld -M reports it at one place but 
it seems to get offset somewhere in the loading/relocating..Where I have 
no idea (yet)... 

BTW shouldn't the SCBB register point to where the SCB is therefore you 
could in reality load the SCB wherever?

Also, what _exactly_ does SCB2NDINT mean?


Karl


------------------------------------------------------------------------------

Karl Maftoum
Computer Engineering Student at the University of Canberra, Australia

Email: k.maftoum@student.canberra.edu.au